Bug 1211054

Summary: Failed to start VM after upgrade from 6.5 to 6.6
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-nodeAssignee: Ryan Barry <rbarry>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.5.1CC: bmcclain, cshao, dfediuck, ecohen, fdeutsch, gklein, hadong, huiwa, leiwang, lsurette, mkalinin, rbarry, tlitovsk, yaniwang, ycui, ylavi
Target Milestone: ---Keywords: Regression, ZStream
Target Release: 3.5.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: node
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, virtual machines failed to start after RHEV-H was upgraded from 6.5 to 6.6. This issue has now been resolved; upgrading RHEV-H to 6.6 no longer hinders the startup of virtual machines.
Story Points: ---
Clone Of: 1207155 Environment:
Last Closed: 2015-04-28 18:54:08 UTC Type: ---
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: 1207155    
Bug Blocks:    

Comment 3 cshao 2015-04-24 05:43:13 UTC
Test version:
RHEVH 6.5 20150115
rhev-hypervisor6-6.6-20150421.0
ovirt-node-3.2.2-3.el6.noarch
ovirt-node-3.2.2-3.el6.noarch
RHEV-M VT14.3 (3.5.1-0.4.el6ev)

Test steps:
1. Installed RHEVH 6.5 20150115 with dhcp network, 
2. Add rhevh via rhevm portal into 3.4 compatibility version in rhevm
4. Created 1 VM running on it successful.
5. Shutdown the 1 VM, then maintenance the rhevh 6.5 host.
6. Upgrade rhevh 6.5 via rhevm portal to rhev-hypervisor6-6.6-20150421.0
7. Start the VM

Actual results:
Start VM can succeed after upgrade from 6.5 to 6.6.

So the bug is fixed by above build, change bug status to VERIFIED.

Comment 5 errata-xmlrpc 2015-04-28 18:54:08 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.

https://rhn.redhat.com/errata/RHBA-2015-0903.html