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

Bug 928589

Summary: RHEV-H status show "Install failed" with RHEVM-SF build after upgrade from old 6.4 to latest 6.4
Product: Red Hat Enterprise Virtualization Manager Reporter: cshao <cshao>
Component: vdsmAssignee: Barak <bazulay>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: urgent    
Version: 3.2.0CC: alonbl, bazulay, chchen, gouyang, hadong, hateya, huiwa, iheim, leiwang, lpeer, mburns, ycui, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-29 19:15:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine.log
none
vdsm.log none

Description cshao 2013-03-28 02:31:03 UTC 
Description of problem:
RHEV-H status show "Install failed" with RHEVM-SF build after upgrade from old 6.4 to latest 6.4

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20130318.1.el6_4
RHEVM SF11

How reproducible:
100%

Steps to Reproduce:
1. Install the old 6.4 version on one machine
(e.g. rhev-hypervisor6-6.4-20130227.0.el6_4).
2. Register to rhevm-sf build with compatibility version 3.1.
3. Upgrade RHEV-H to latest version (rhev-hypervisor6-6.4-20130318.1.el6_4) via RHEVM.
  
Actual results:
1. RHEV-M side: RHEV-H status show "Install failed".
2. RHEV-H can up if user click the "Activate" button manual.
3. RHEV-H side: RHEV-H upgrade can successful, nic can up.
4. The same issue occurs if upgrade from "6.3 update 6.1 with 3.1GA" to "6.4 latest".

Expected results:
RHEV-H status show "up" with RHEVM-SF build after upgrade from old 6.4 to latest 6.4.

Additional info:
Comment 1 cshao 2013-03-28 02:32:31 UTC 
Created attachment 717407 [details]
engine.log
Comment 2 cshao 2013-03-28 02:33:08 UTC 
Created attachment 717408 [details]
vdsm.log
Comment 3 Alon Bar-Lev 2013-03-29 19:15:03 UTC 
Probably an old bug... notice the missing space after the 'OK'

Well, this is already fixed by Douglas in bug#920671.

2013-03-28 17:16:12,922 ERROR [org.ovirt.engine.core.bll.InstallerMessages] (OVirtNodeUpgrade) Installation of Host. Received illegal XML from Host. Message: <BSTRAP component='RHEL_INSTALL' status='OK'message='vdsm daemon stopped for upgrade process!'/>: org.ovirt.engine.core.compat.CompatException: Element type "BSTRAP" must be followed by either attribute specifications, ">" or "/>".
	at org.ovirt.engine.core.compat.backendcompat.XmlDocument.LoadXml(XmlDocument.java:48) [engine-compat.jar:]
	at org.ovirt.engine.core.bll.InstallerMessages._internalPostOldXmlFormat(InstallerMessages.java:92) [engine-bll.jar:]
	at org.ovirt.engine.core.bll.InstallerMessages.postOldXmlFormat(InstallerMessages.java:73) [engine-bll.jar:]
	at org.ovirt.engine.core.bll.OVirtNodeUpgrade._threadMain(OVirtNodeUpgrade.java:76) [engine-bll.jar:]
	at org.ovirt.engine.core.bll.OVirtNodeUpgrade.access$100(OVirtNodeUpgrade.java:27) [engine-bll.jar:]
	at org.ovirt.engine.core.bll.OVirtNodeUpgrade$2.run(OVirtNodeUpgrade.java:107) [engine-bll.jar:]
	at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_11-icedtea]

*** This bug has been marked as a duplicate of bug 920671 ***