Hide Forgot
Created attachment 1526736 [details] rename log Description of problem: Running ovirt-engine-rename fails with [ ERROR ] Failed to execute stage 'Setup validation': 'changed' Version-Release number of selected component (if applicable): ovirt-engine-4.3.0.4-0.1.el7.noarch How reproducible: always on my d/s 4.3 engines Steps to Reproduce: 1. run /usr/share/ovirt-engine/setup/bin/ovirt-engine-rename 2. enter new hostname and yes to all 3. Actual results: rename failed, see attached log Expected results: rename is successful Additional info: postgresql.conf doesn't have 'changed' key: ENV OVESETUP_CORE/uninstallFilesInfo=dict:'{'/etc/pki/ovirt-engine/keys/reports.key.nopass': {'changed': False, 'groups': ['ca_pki'], 'md5': 'f6f3714166918f150d2528a9bb10d901'}, '/var/opt/rh/rh-postgresql95/lib/pgsql/data/postgresql.conf': {'groups': ['core', 'unremovable'], 'md5': '415d91ef1aa820745278fc82866fe229'}, '/etc/httpd/conf.d/ovirt-engine-root-redirect.conf': {'changed': False, 'groups': ['core'], 'md5': '161fc2c071d4bd8973796008e5fea7b8'}, '/etc/pki/ovirt-engine/cacert.conf': {'changed': False, 'groups': ['ca_pki'], 'md5': 'db0967328f0c2c544fbfc7f93f4dfa1e'} ... There is maybe somehow mixed PG95, that was upgraded to PG10 /var/opt/rh/rh-postgresql95/lib/pgsql/data/postgresql.conf no such file
I think it should already work for you, not sure. Moving to MODIFIED for now. Or, you can test with current upstream master snapshot.
No, sorry, I think it's a real bug.
QE: Reproduction/Verification steps: 1. Setup engine 2. Remove or rename some file that was written by engine-setup. Removal can be done manually, or by a previous run of engine-setup itself over versions - does not matter for current bug. 3. Run ovirt-engine-rename With a broken version, it will fail as described. With the fixed version, it will continue.
Now pushed a similar patch for engine-cleanup, which is also affected the same way. Above steps apply similarly.
Verified in ovirt-engine-4.3.2-0.1.el7.noarch
This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.