Bug 1200430

Summary: [3.5-6.6]TUI crash when setup hosted engine on RHEVH
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-node-plugin-hosted-engineAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.5.1CC: cshao, dougsland, fdeutsch, gklein, huiwa, leiwang, nsednev, yaniwang, ycui, ylavi
Target Milestone: ---Keywords: TestBlocker, Triaged, ZStream
Target Release: 3.5.4Flags: ylavi: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: node
Fixed In Version: ovirt-node-plugin-hosted-engine-0.2.0-10.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1200233 Environment:
Last Closed: 2015-09-03 17:54:44 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: 1200233    
Bug Blocks: 1193058    

Comment 3 Ying Cui 2015-03-13 07:30:05 UTC 
Verified this bug on rhevh 6.6 (20150312.0.el6ev)(ovirt-node-plugin-hosted-engine-0.2.0-10.0.el6ev.x86_64)

# rpm -q ovirt-node-plugin-vdsm ovirt-node-plugin-hosted-engine vdsm ovirt-node ovirt-hosted-engine-ha ovirt-hosted-engine-setup
ovirt-node-plugin-vdsm-0.2.0-20.el6ev.noarch
ovirt-node-plugin-hosted-engine-0.2.0-10.0.el6ev.x86_64
vdsm-4.16.12-2.el6ev.x86_64
ovirt-node-3.2.1-10.el6.noarch
ovirt-hosted-engine-ha-1.2.5-1.el6ev.noarch
ovirt-hosted-engine-setup-1.2.2-1.el6ev.noarch

Here is another TUI error issue already reported the new medium bug 1201632 to trace detail. 
And for comment 2, Nikolai already reported new bug 1200474 to trace different fix.

The original bug report error is fixed, TUI not crash, and setup hosted engine through TUI can be continued. So this testblocker bug is verified. Testing can be continued.
Comment 8 errata-xmlrpc 2015-09-03 17:54:44 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-1733.html