Created attachment 1287950 [details] All logs in /var/log, /tmp and sosreport from host Description of problem: Missing new build boot entry after upgrade to rhvh-4.1-20170613.0 Version-Release number of selected component (if applicable): From: redhat-virtualization-host-4.0-20170307.0 To: redhat-virtualization-host-4.1-20170613.0 How reproducible: 100% Steps to Reproduce: 1. Install rhvh-4.0-20170307.0 2. Login rhvh and setup local repos, upgrade to rhvh-4.1-20170613.0 # yum update 3. Reboot and focus on boot entry Actual results: After step 3, missing new build boot entry, only one old build boot entry: --------------------- rhvh-4.0-0.20170307.0 tboot 1.9.4 --------------------- Expected results: After step 3, should show both two build boot entry, just looks like. --------------------- rhvh-4.1-0.20170613.0 rhvh-4.0-0.20170307.0 tboot 1.9.4 --------------------- Additional info: No such issue in redhat-virtualization-host-4.1-20170609.2, so this is a regression bug.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Since this is 7.4 only, we may want to move to 4.1.5
(In reply to Ryan Barry from comment #2) > Since this is 7.4 only, we may want to move to 4.1.5 earlier is better to unblock RHVH 7.4 upgrade testing. Thanks.
There will be a patch/build sooner. I just meant the targeted version.
This is crazy -- The LVM team has made a breaking change in 7.4. In 7.4, /etc/lvm/lvm.conf now defaults to "units = r" If /etc is bind mounted from the 7.4 image to the 7.3 image (which imgbased does to do some fstab work), lvm commands immediately segfault with "Invalid Units Specification", even if "--units" is passed. Instead, we must copy off the new LVM config, substitute the old, then copy the new one back once we're done.
Test version: From: redhat-virtualization-host-4.0-20170307.0 To: redhat-virtualization-host-4.1-20170622.3(RHEL7.4) imgbased-0.9.32-0.1.el7ev.noarch Test steps: 1. Install rhvh-4.0-20170307.0 2. Login rhvh and setup local repos, upgrade to rhvh-4.1-20170622.3 # yum update 3. Reboot and focus on boot entry Test results: After step 3, there are both new and old build boot entries, can access new build successful. So this bug is fixed in redhat-virtualization-host-4.1-20170622.3, I will change the status to VERIFIED after the status is changed to ON_QA.
According to comment 6, change the status to VERIFIED.