Description of problem: Currently, it's possible to: 1. install and setup version X 2. yum update ovirt-engine-setup 3. engine-cleanup This might fail in unexpected/unintended ways, or worse, not fail but cause unexpected consequences. We have code (currently in packaging/setup/plugins/ovirt-engine-remove/base/core/misc.py) that was intended to (also) prevent that with 3.2->3.3, but it won't prevent 3.3+ against later versions.
This fails on master with: [ ERROR ] Cleanup utility and installed version mismatch Please use a version of cleanup utility that matches the engine installed version (now engine-cleanup 3.6.0, engine 3.6.0_master) [ ERROR ] Failed to execute stage 'Environment setup': Cleanup utility version mismatch Not moving the bug back because this probably affects only master (and the bug is on 3.5). Worked around by setting: RPM_VERSION = '3.6.0_master' in /usr/share/ovirt-engine/setup/ovirt_engine_setup/config.py . Simone - please have a look. Thanks!
Thanks Didi, I added an additional patch to check just just the x.y.z part of version number ignoring any suffix (_pre, _master, _custom...)
*** Bug 1128413 has been marked as a duplicate of this bug. ***
*** Bug 1130137 has been marked as a duplicate of this bug. ***
Possibly an implication of the bug described here? Trying to run engine cleanup I get: "***L:ERROR Internal error: No module named paramiko" Only after "yum install python-paramiko" I get "Cleanup utility and installed version mismatch"
No, paramiko was required just from here but it's a different feature and the dependencies look ok. http://gerrit.ovirt.org/#/c/33231/ Can you please post the list of rpm you are using?
oVirt 3.5 has been released and should include the fix for this issue.
Missed this by mistake, I do not have the relevant env anymore. Please ignore if this does not reproduce.