Created attachment 1308672 [details] log for upgrade error Description of problem: Missing new layer boot entry sometimes when upgrade to rhvh-4.1-20170802 Version-Release number of selected component (if applicable): Old version: rhvh-4.0-0.20170307.0 New version: redhat-virtualization-host-4.1-20170802.0 vdsm-4.19.24-1.el7ev.x86_64 kernel-3.10.0-693.el7.x86_64 imgbased-0.9.38-0.1.el7ev.noarch How reproducible: About 40% Steps to Reproduce: 1. Clean install rhvh-4.0-0.20170307.0 2. Set local repo and run #yum update 3. Reboot and log in new layer boot entry Actual results: 1. After step 3, missing new layer boot entry rhvh-4.1-0.20170802.0 Expected results: 1. After step 3, New layer boot entry could display and can successfully log in Additional info: Auto test also reproduce this issue: 1. From redhat-virtualization-host-4.1-20170616.0.x86_64 to redhat-virtualization-host-4.1-20170802.0 via "rhevm" side 2. From redhat-virtualization-host-4.0-20170307.1.x86_64 to redhat-virtualization-host-4.1-20170802.0 via "yum install *.rpm"
Created attachment 1308678 [details] imgbased.log
Still encountered this issue in imgbased-0.9.39-0.1.el7ev(rhvh-4.1-20170804), and 100% reproducible in QE test ENV. Totally tested 8 times with different machines, all can reproduce this issue. So this bug is not fixed in imgbased-0.9.39-0.1.el7ev.
Update: We have test this bug on rhvh-4.1-20170808.0 build Version-Release number of selected component (if applicable): redhat-virtualization-host-4.1-20170808.0 imgbased-0.9.41-0.1.el7ev.noarch Step to test: --- the way 1 --- 1. Clean install rhvh-4.1-20170808.0 2. Set local repo 3. Upgrade build via "yum update" or "yum install *rpm" 4. Reboot and log in new layer boot entry --- the way 2 --- Auto test Test results: 1. After step 4, New layer boot entry could display and can successfully log in Additional info: In order to prevent the probability about this bug on missing boot entry we have test on iscsi, FC, uefi, local machines, in use of auto and manual testing about more than 30 times, all above tests are successful According our test results, I think this bug is fixed on rhvh-4.1-20170808.0 build, so I will change status into VERIFIED jiawu