Description of problem: Engine-cleanup utility moves postgres conf files to backup files with timestamps. However without these files postgres is unable to start. Thus process of engine-cleanup && engine-setup needs manual intervention of creating new conf files. These files should either be just copied to bakcups, if possible even backed up to original state before engine was installed. Version-Release number of selected component (if applicable): otopi-1.7.2-0.0.master.20170725102025.git770a428.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. run engine-cleanup 2. try to run engine-setup (fails on database conf files missing) 3. mv /var/lib/pgsql/data/postgresql.conf.20170725150124 /var/lib/pgsql/data/postgresql.conf 4. mv /var/lib/pgsql/data/pg_hba.conf.20170725150124 /var/lib/pgsql/data/pg_hba.conf 5. run engine setup -> success Actual results: Need manual creation of new conf files. Expected results: These conf files should be a) on engine-setup created by engine setup not just edited or b) on engine-cleanup copied not moved to backup or c) on engine-cleanup restored from backup of conf files created by engine-setup Additional info:
Verified on version: otopi-1.7.2-0.0.master.20170816071636.git7a3278c.el7.centos.noarch engine-cleanup create copy of config file
*** Bug 1456727 has been marked as a duplicate of this bug. ***
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.