Bug 867562

Summary: Upgrade script should successfully terminate before reboot occurs
Product: Red Hat Enterprise Linux 6 Reporter: Chris Pelland <cpelland>
Component: ovirt-nodeAssignee: Mike Burns <mburns>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.3CC: acathrow, alonbl, bazulay, bsarathy, chetan, cpelland, cshao, fdeutsch, gouyang, iheim, istein, jboggs, leiwang, mburns, ovirt-maint, pm-eus, sgordon, ycui
Target Milestone: rcKeywords: TestBlocker, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-2.3.0-15.el6_3.13 Doc Type: Bug Fix
Doc Text:
On completion of Hypervisor upgrades the Hypervisor is rebooted. Previously this reboot was performed from within the shell session responsible for performing the upgrade. This resulted in the status of the host being listed in the Manager as "Install Failed" - even when the upgrade was successful. The rhev-hypervisor6 package has been updated. On upgrades the shell session is now allowed to finish gracefully while the reboot is initiated in the background.
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-06 15:25:38 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: 847103    
Bug Blocks:    

Description Chris Pelland 2012-10-17 18:12:51 UTC
This bug has been copied from bug #847103 and has been proposed
to be backported to 6.3 z-stream (EUS).

Comment 10 errata-xmlrpc 2012-11-06 15:25:38 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/RHBA-2012-1425.html

Comment 11 Mike Burns 2013-03-08 12:44:16 UTC
*** Bug 916485 has been marked as a duplicate of this bug. ***