Bug 627538

Summary: System will not boot sometimes when using rhevm to do upgrade twice.
Product: Red Hat Enterprise Linux 5 Reporter: Alan Pevec <apevec>
Component: ovirt-nodeAssignee: Mike Burns <mburns>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: 5.6CC: avettath, cpelland, cshao, dyasny, fyu, leiwang, liko, llim, lyarwood, mburns, mjenner, moli, mshao, ovirt-maint, rdassen, sgordon, syeghiay, vbian, xinsun, ycui, yeylon
Target Milestone: rcKeywords: OtherQA, TestOnly
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Under certain circumstances, using Red Hat Enterprise Virtualization Manager to perform more than one upgrade of a Red Hat Enterprise Virtualization Hypervisor installation in a successive order would render the Hypervisor unable to boot. With this update, the ovirt-config-boot script has been modified to address this issue, and Red Hat Enterprise Virtualization Hypervisor can now be upgraded as expected.
Story Points: ---
Clone Of: 582999 Environment:
Last Closed: 2012-02-21 05:02:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 582999, 628666    

Comment 5 Mohua Li 2010-11-18 06:07:43 UTC
according to comment4, and also, we try many upgrade test in our acceptance, but we also can't reproduce this bug, seems the same as 582999, so, Alan, could you invlove the customer to verify this bug?

Comment 6 Yewei Shao 2010-12-11 10:53:58 UTC
Add the keyword to OtherQA based on the comment #5.

Comment 7 Alan Pevec 2011-01-05 10:06:51 UTC
It is the same as 582999 where customer still sees the issue, so moving to the next 5.6 update.

Comment 8 Alan Pevec 2011-01-05 10:08:47 UTC
*** Bug 582999 has been marked as a duplicate of this bug. ***

Comment 9 Jaromir Hradilek 2011-01-06 15:55:30 UTC
    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:
Under certain circumstances, using Red Hat Enterprise Virtualization Manager to perform more than one upgrade of a Red Hat Enterprise Virtualization Hypervisor installation in a successive order could render the Hypervisor unable to boot. With this update, the ovirt-config-boot script has been modified to address this issue, and Red Hat Enterprise Virtualization Hypervisor can now be upgraded as expected.

Comment 33 Ying Cui 2011-12-15 06:15:25 UTC
Change status to 'Verified' according to comment 28 and comment 32

Comment 36 Stephen Gordon 2012-02-10 14:37:35 UTC
    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 @@
-Under certain circumstances, using Red Hat Enterprise Virtualization Manager to perform more than one upgrade of a Red Hat Enterprise Virtualization Hypervisor installation in a successive order could render the Hypervisor unable to boot. With this update, the ovirt-config-boot script has been modified to address this issue, and Red Hat Enterprise Virtualization Hypervisor can now be upgraded as expected.+Under certain circumstances, using Red Hat Enterprise Virtualization Manager to perform more than one upgrade of a Red Hat Enterprise Virtualization Hypervisor installation in a successive order would render the Hypervisor unable to boot. With this update, the ovirt-config-boot script has been modified to address this issue, and Red Hat Enterprise Virtualization Hypervisor can now be upgraded as expected.

Comment 37 errata-xmlrpc 2012-02-21 05:02:43 UTC
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/RHSA-2012-0168.html