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

Bug 1181586

Summary: engine-setup unconditionally enables the engine if ran on dwh on separate host
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-engine-setupAssignee: Yedidyah Bar David <didi>
Status: CLOSED ERRATA QA Contact: Petr Matyáš <pmatyas>
Severity: urgent Docs Contact:
Priority: high    
Version: 3.5.0CC: bazulay, didi, ecohen, gklein, iheim, lsurette, pstehlik, rbalakri, Rhev-m-bugs, sbonazzo, sherold, yeylon, ylavi
Target Milestone: ---Keywords: ZStream
Target Release: 3.5.1Flags: ylavi: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: org.ovirt.engine-root-3.5.1-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1174667 Environment:
Last Closed: 2015-04-28 18:43:34 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: 1174667    
Bug Blocks: 1193058, 1197441    

Comment 1 Yedidyah Bar David 2015-01-21 13:11:03 UTC 
Note to QE - should not be reproducible on reports alone, only on dwh alone - reports does not access the engine db.
Comment 2 Sandro Bonazzola 2015-02-20 11:07:48 UTC 
Automated message: can you please update doctext or set it as not required?
Comment 4 Petr Matyáš 2015-03-03 12:17:04 UTC 
Engine is not actually set up on dwh machine, but the dwh asks again for all the credentials like hosts dns name and password. I don't think it's the desired behaviour. Am I wrong?
Comment 5 Yedidyah Bar David 2015-03-03 12:55:43 UTC 
After checking the logs (thanks, Petr!), it seems no questions were asked again.

Installing the engine also installs websocket-proxy, and if you accept the default Yes for 'Configure WebSocket Proxy on this host?', you'll be asked about it too. That's unrelated to dwh.
Comment 6 errata-xmlrpc 2015-04-28 18:43:34 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/RHSA-2015-0888.html