Bug 1059358 - RHEVM SETUP REMOTE_DB: postgresProvisioning remains none in answer file
Summary: RHEVM SETUP REMOTE_DB: postgresProvisioning remains none in answer file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-setup
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 3.3.1
Assignee: Ofer Schreiber
QA Contact: sefi litmanovich
URL:
Whiteboard: integration
Depends On: 1040590
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-29 17:33 UTC by rhev-integ
Modified: 2014-03-03 13:32 UTC (History)
10 users (show)

Fixed In Version: is34
Doc Type: Bug Fix
Doc Text:
Previously, running engine-setup with the option to create an answer file enabled would successfully create an answer file, but users would still be prompted to select whether the engine database was hosted locally or remotely when using that answer file in subsequent setups. With this update, the answer file now correctly records whether the user elected to use a local or remote database during the setup process.
Clone Of: 1040590
Environment:
Last Closed: 2014-03-03 13:32:38 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0227 0 normal SHIPPED_LIVE rhevm 3.3.1 bug fix update 2014-03-03 18:29:31 UTC
oVirt gerrit 23832 0 None None None Never
oVirt gerrit 23854 0 None None None Never
oVirt gerrit 23900 0 None None None Never

Comment 2 sefi litmanovich 2014-02-06 17:23:49 UTC 
Verified on RHEL6.5, RHEVM3.3.1 IS34.
Comment 4 errata-xmlrpc 2014-03-03 13:32:38 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.

http://rhn.redhat.com/errata/RHBA-2014-0227.html
Note You need to log in before you can comment on or make changes to this bug.