Created attachment 1257994 [details] Sosreport, all logs and /boot/grub2/grub.cfg Description of problem: Miss boot entry of RHVH 4.1 after upgrade with "yum install *update*.rpm" Version-Release number of selected component (if applicable): From: redhat-virtualization-host-4.0-20160919.0 To: redhat-virtualization-host-4.1-20170222.0 imgbased-0.9.13-0.1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Clean install redhat-virtualization-host-4.0-20160919.0 2. Reboot and login rhvh 4.0, download update rpm redhat-virtualization-host-image-update-4.1-20170222.0.el7_3.noarch.rpm, update with: # yum install redhat-virtualization-host-image-update-4.1-20170222.0.el7_3.noarch.rpm 3. Reboot host, and focus on boot entry during reboot Actual results: 1. After step 3, there is no boot entry of rhvh-4.1-0.20170222.0, so can not access new build after upgrade Expected results: After step 3, there should be boot entry of rhvh-4.1-0.20170222.0, and can access new build after upgrade Additional info: 1. No such issue when upgrade with command "yum update"(but it has another bug 1427082) 2. No such issue in build redhat-virtualization-host-4.1-20170208.0, so this is regression bug.
Also encounter this bug with below two scenarios: 1. Upgrade from rhvh-4.0-0.20161116.0 to redhat-virtualization-host-4.1-20170222.0 with "# yum update" 2. Upgrade from rhvh-4.1-0.20170202.0 to redhat-virtualization-host-4.1-20170222.0 in rhvm side.
Added keywords TestBlocker according to comment 0 and comment 1. But no such issue when upgrade from rhvh-4.0-0.20160919.0 to redhat-virtualization-host-4.1-20170222.0 with "# yum update", so not totally blocker.
The new respin imgbased rpm(imgbased-0.9.14-0.1.el7ev) was built ready, but there is NO RHVH 4.1.1 new build to QE to include this imgbased. So the bug is not ready for testing, although it is ON_QA.
Test version: From: redhat-virtualization-host-4.0-20160919.0 To: redhat-virtualization-host-4.1-20170308.1 imgbased-0.9.17-0.1.el7ev.noarch Steps to Reproduce: 1. Clean install redhat-virtualization-host-4.0-20160919.0 2. Reboot and login rhvh 4.0, download update rpm redhat-virtualization-host-image-update-4.1-20170308.1.el7_3.noarch.rpm, update with: # yum install redhat-virtualization-host-image-update-4.1-20170308.1.el7_3.noarch.rpm 3. Reboot host, and focus on boot entry during reboot Test results: 1. After step 3, there are both two build boot entries of rhvh-4.1-0.20170309 and rhvh-4.0-0.20160919 Additional info: Also no such issue in below two scenarios: 1. Upgrade from rhvh-4.0-0.20161116.0 to redhat-virtualization-host-4.1-20170308.1 with "# yum update" 2. Upgrade from rhvh-4.0-0.20161116.0 to redhat-virtualization-host-4.1-20170308.1 with "# yum install redhat-virtualization-host-image-update-4.1-20170308.1.el7_3.noarch.rpm" So this bug is fixed in imgbased-0.9.17-0.1.el7ev.noarch, change the status to VERIFIED.