Description of problem:
With 6.6 we need to set the correct wwid on the kernel commandline during boot.
On fresh 6.6 installations this is done by the installer.
But the upgrade logic needs to be improved to cover the case where a user with a multipath disk is upgarding rhev-h.
This scenario is already covered by the current implementation.
# cat /etc/system-release
Red Hat Enterprise Virtualization Hypervisor 6.6 (20150128.0.el6ev)
# rpm -q ovirt-node kernel
kernel /vmlinuz0 root=live:LABEL=Root ro rootfstype=auto rootflags=ro ksdevice=bootif max_loop=256 crashkernel=128M lang= rd_NO_LUKS RD_NO_LVM rd_NO_MD quiet elevator=deadline rhgb rd_NO_DM mpath.wwid=360a9800050334c33424b334163434546
After upgrade from rhevh 6.5 for 3.4.z(RHEV-H 6.5-20150115.0.el6ev
) to 20150128.0.el6ev. wwid already kernel cmdline after upgrade, and rhevh 6.6 start successful.
And the backup rhevh 6.5 for 3.4.z(RHEV-H 6.5-20150115.0.el6ev) also can boot successful.
Test machine is Z600-03
So this bug is verified on rhevh side, and the kernel bug 1179728 was fixed yet as well.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.