I’ve noticed something that may be related. I have two hosts that had 4.03
installed from the ISO (from console of the host), and two with 4.0.4 (also
from an ISO). At various points since going from engine 3.6 to 4.04 to 4.05,
we’ve had the ‘upgrade available’ message pop up on all 4 hosts, and in each
case I’ve put the host in maintenance mode and let it run the ‘upgrade’. They
don’t generate any errors; they reboot and report a finished upgrade. But they
still report as being 4.03 and 4.04 hosts.
When I manually run ‘yum update’ from any of the hosts, they report ‘no
packages marked for update’.
Update – After looking more closely, it looks like most repos are disabled on
the hosts. I’m not sure how it got to that state as I never would have disabled
them:
[root@labvmhostt03 etc]# yum repolist all
Loaded plugins: fastestmirror, imgbased-warning
Warning: yum operations are not persisted across upgrades!
Loading mirror speeds from cached hostfile
* ovirt-4.0: mirror.linux.duke.edu
* ovirt-4.0-epel: mirror.nexcess.net
repo id repo name
status
C7.0.1406-base/x86_64 CentOS-7.0.1406
- Base
disabled
C7.0.1406-centosplus/x86_64 CentOS-7.0.1406
- CentOSPlus
disabled
C7.0.1406-extras/x86_64 CentOS-7.0.1406
- Extras
disabled
C7.0.1406-fasttrack/x86_64 CentOS-7.0.1406
- CentOSPlus
disabled
C7.0.1406-updates/x86_64 CentOS-7.0.1406
- Updates
disabled
C7.1.1503-base/x86_64 CentOS-7.1.1503
- Base
disabled
C7.1.1503-centosplus/x86_64 CentOS-7.1.1503
- CentOSPlus
disabled
C7.1.1503-extras/x86_64 CentOS-7.1.1503
- Extras
disabled
C7.1.1503-fasttrack/x86_64 CentOS-7.1.1503
- CentOSPlus
disabled
C7.1.1503-updates/x86_64 CentOS-7.1.1503
- Updates
disabled
!base/7/x86_64 CentOS-7 - Base
disabled
base-debuginfo/x86_64 CentOS-7 -
Debuginfo
disabled
base-source/7 CentOS-7 - Base
Sources
disabled
c7-media CentOS-7 -
Media
disabled
centos-ovirt40-release/x86_64 CentOS-7 -
oVirt 4.0
enabled: 365
centosplus/7/x86_64 CentOS-7 - Plus
disabled
centosplus-source/7 CentOS-7 - Plus
Sources
disabled
cr/7/x86_64 CentOS-7 - cr
disabled
!extras/7/x86_64 CentOS-7 -
Extras
disabled
extras-source/7 CentOS-7 -
Extras Sources
disabled
fasttrack/7/x86_64 CentOS-7 -
fasttrack
disabled
!group_cockpit-cockpit-preview/x86_64 Copr repo for
cockpit-preview owned by @cockpit
disabled
ovirt-4.0/7 Latest oVirt
4.0 Release
enabled: 908
ovirt-4.0-centos-gluster37/x86_64 CentOS-7 -
Gluster 3.7
enabled: 214
ovirt-4.0-epel/x86_64 Extra Packages
for Enterprise Linux 7 - x86_64
enabled: 11,145
ovirt-4.0-patternfly1-noarch-epel/x86_64 Copr repo for
patternfly1 owned by patternfly
enabled: 2
!updates/7/x86_64 CentOS-7 -
Updates
disabled
updates-source/7 CentOS-7 -
Updates Sources
disabled
!virtio-win-stable virtio-win
builds roughly matching what was shipped in latest RHEL
enabled: 4
repolist: 12,638
Here’s what I did to fix on each host:
Put into maintenance mode
mv -f /etc/yum.repos.d/ovirt-4.0.repo /var/tmp/ovirt-4.0.repo.$(date +%F)
mv -f /etc/yum.repos.d/ovirt-4.0-dependencies.repo
/var/tmp/ovirt-4.0-dependencies.repo.$(date +%F)
yum-config-manager --enable CentOS-7
yum-config-manager --enable CentOS-7 - Updates
yum-config-manager --enable CentOS-7 - Base
yum localinstall http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm
yum –y update
reboot
activate host; confirm it shows up as 4.06 host
Daniel
From: <[email protected]> on behalf of Yuval Turgeman <[email protected]>
Date: Thursday, February 9, 2017 at 2:51 AM
To: Thomas Kendall <[email protected]>
Cc: Ryan Barry <[email protected]>, "[email protected]" <[email protected]>
Subject: Re: [ovirt-users] Upgrading oVirt-Node-NG from 4.0.3 to 4.0.6
Hi, so 4.0.6 was downloaded but it is not upgrading the node ?
On Fri, Feb 3, 2017 at 11:58 PM, Thomas Kendall
<[email protected]<mailto:[email protected]>> wrote:
We recently migrated from 3.6 to 4.0, but I'm a little confused about how to
keep the nodes up to date. I see the auto-updates come through for my 4.0.3
nodes, but they don't seem to upgrade them to the newer 4.0.x releases.
Is there a way to do this upgrade? I have two nodes that were installed with
4.0.3, and I would like to bring them up to the same version as everything else.
For reference, the 4.0.3 nodes were built off the 4.0-2016083011 iso, and the
4.0.6 nodes were built off the 4.0-2017011712 iso.
Thanks,
Thomas
_______________________________________________
Users mailing list
[email protected]<mailto:[email protected]>
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users
