Created attachment 1324965 [details] engine-setup output.log Description of problem: Running ${TARGET}/bin/engine-setup fails if running more that once in developer environment. Workaround: remove ${TARGET}/etc/ovirt-engine/engine.conf.d/10-setup-database.conf before running ovirt-setup Version-Release number of selected component (if applicable): 4.2 master, commit 0ae56b88a5 How reproducible: 100% Steps to Reproduce: 1. Compile engine to a directory further referenced as ${TARGET} 2. Run ${TARGET}/bin/engine-setup in dev mode 3. Run ${TARGET}/bin/engine-setup in dev mode Actual results: engine-setup fails Expected results: engine-setup properly configures the engine Additional info:
Created attachment 1324966 [details] engine-setup.log
Relates to http://lists.ovirt.org/pipermail/devel/2017-September/031313.html discussion.
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.
Verified that engine-setup can be executed twice in row in dev mode on current master (commit 86aaddda83) and with otopi-1.7.2-0.0.master.20170912135518.git85923b3.fc26.noarch
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.