Bug 1250944 - missing vmconsole related answer in the answer file for automated install
Summary: missing vmconsole related answer in the answer file for automated install
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-live
Classification: Retired
Component: General
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-3.6.0-rc
: 3.6.0
Assignee: Sandro Bonazzola
QA Contact: Pavol Brilla
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-06 11:09 UTC by Sandro Bonazzola
Modified: 2015-11-27 07:48 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-11-27 07:48:53 UTC
oVirt Team: ---
Embargoed:
rule-engine: ovirt-3.6.0+
rule-engine: blocker+
ylavi: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 44114 0 master MERGED setup: answer: added answers to vmconsole-proxy Never
oVirt gerrit 44488 0 ovirt-live-3.6 MERGED setup: answer: added answers to vmconsole-proxy Never

Description Sandro Bonazzola 2015-08-06 11:09:29 UTC
missing vmconsole related answer in the answer file for automated install.
automated install is currently asking question, marking as regression

Comment 1 Red Hat Bugzilla Rules Engine 2015-09-22 07:43:50 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 2 Pavol Brilla 2015-11-26 12:14:24 UTC
OVESETUP_CONFIG/websocketProxyConfig=bool:True
verified on rhevm-3.6.0.3-0.1.el6.noarch

Comment 3 Pavol Brilla 2015-11-26 12:15:15 UTC
wrong copy&paste, correct value
OVESETUP_VMCONSOLE_PROXY_CONFIG/vmconsoleProxyConfig=bool:True

Comment 4 Sandro Bonazzola 2015-11-27 07:48:53 UTC
Since oVirt 3.6.0 has been released, moving from verified to closed current release.


Note You need to log in before you can comment on or make changes to this bug.