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.