Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1105873 - [RHEVM-SETUP] - upgrade of dwh fails using previously generated answer file
Summary: [RHEVM-SETUP] - upgrade of dwh fails using previously generated answer file
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-dwh
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.4.0
Assignee: Yedidyah Bar David
QA Contact: Barak Dagan
Whiteboard: integration
Depends On: 1094016
TreeView+ depends on / blocked
Reported: 2014-06-08 12:16 UTC by Yedidyah Bar David
Modified: 2014-06-08 12:34 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Cause: setup code of 3.3 only allowed having the dwh db on the same host and port of the engine db, and did not keep the host and port in its own conf file, relying on the engine's. setup code of 3.4 does allow different hosts and does keep db host and port for dwh in the dwh conf file. Consequence: Due to a difference in the initialization order of internal state, an upgrade from 3.3 to 3.4.0 using an answer file does not set the correct db host and port, which causes it to fail. Workaround (if any): To make upgrade from 3.3 to 3.4.0 with an answer file not fail, copy the db host and port from the engine to dwh's conf file, using this command: sed -rne 's/^ENGINE_DB_(HOST|PORT)=(.*)/DWH_DB_\1=\2/p' \ < /etc/ovirt-engine/engine.conf.d/10-setup-database.conf \ >> /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-database.conf Result: setup will not fail on upgrade of dwh of 3.3 to 3.4 with an answer file due to this issue.
Clone Of: 1100281
Last Closed: 2014-06-08 12:31:42 UTC
oVirt Team: ---
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
oVirt gerrit 27693 None None None Never
oVirt gerrit 28008 None None None Never
oVirt gerrit 28105 None None None Never

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