Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1427088

Summary: Miss boot entry of RHVH 4.1 after upgrade with "yum install *update*.rpm"
Product: [oVirt] ovirt-node Reporter: Huijuan Zhao <huzhao>
Component: Installation & UpdateAssignee: Ryan Barry <rbarry>
Status: CLOSED CURRENTRELEASE QA Contact: Huijuan Zhao <huzhao>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.1CC: bugs, cshao, dguo, dougsland, jiawu, leiwang, qiyuan, rbarry, sbonazzo, weiwang, yaniwang, ycui, yzhao
Target Milestone: ovirt-4.1.1Keywords: Regression, TestBlocker
Target Release: 4.1Flags: rule-engine: ovirt-4.1+
rule-engine: blocker+
sbonazzo: devel_ack+
cshao: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: imgbased-0.9.14-0.1.el7ev Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-21 09:34:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1364040    
Attachments:
Description Flags
Sosreport, all logs and /boot/grub2/grub.cfg none

Description Huijuan Zhao 2017-02-27 10:41:50 UTC 
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.
Comment 1 Huijuan Zhao 2017-03-01 05:24:54 UTC 
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.
Comment 2 Huijuan Zhao 2017-03-01 05:59:57 UTC 
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.
Comment 3 Ying Cui 2017-03-06 13:16:35 UTC 
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.
Comment 4 Huijuan Zhao 2017-03-10 08:07:07 UTC 
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.