Hide Forgot
Description of problem: Upgrade RHEV-H with "upgrade" parameter failed in determine Root partition Version-Release number of selected component (if applicable): rhev-hypervisor6-6.3-20120330.0.el6 How reproducible: 100% Steps to Reproduce: 1. Install RHEV-H and reboot. 2. Upgrade RHEV-H with "linux upgrade" parameter. Actual results: Starting ovirt-firstboot: installing the image. unable to determine Root partition Apr 10 07:07:54 Automatic installation failed. Please review console messages. Apr 10 07:07:54 Press Enter to drop to emergency shell. Expected results: Upgrade RHEV-H with "upgrade" parameter can successful. Additional info: There is no such issue in rhev-hypervisor6-6.2-20120409.0.el6_2, so it is a regression bug.
Verified with rhevh-6.3-20120509.1, rhev-h update with "linux upgrade" successes without any exception. The updated rhev-h boots up successfully.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: In some upgrade situations, the upgrade would fail to find the Root partition correctly. This was due to findfs commands occasionally returning pointers to /dev/dm-* devices instead of /dev/mapper/<wwid> devices. The output from findfs is now run through a translation function that will resolve it to /dev/mapper in all situations.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -In some upgrade situations, the upgrade would fail to find the Root partition correctly. This was due to findfs commands occasionally returning pointers to /dev/dm-* devices instead of /dev/mapper/<wwid> devices. The output from findfs is now run through a translation function that will resolve it to /dev/mapper in all situations.+When upgrading, the Hypervisor would sometimes fail to find the root partition correctly. This was due to findfs commands occasionally returning pointers to /dev/dm-* devices instead of /dev/mapper/<wwid> devices. The output from findfs is now run through a translation function that will resolve devices to a location under /dev/mapper in all cases.
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. http://rhn.redhat.com/errata/RHBA-2012-0741.html