Hide Forgot
Description of problem: rhevm-setup-plugins has code to version-lock dwh/reports if found on the system, even if not configured. See also bug 1098191. It might have made sense at the time, because in 3.2/3.3 dwh/reports' setup were not engine-setup plugins but separate utilities. Need to map all relevant flows and consider dropping this code altogether. If we decide to keep it, probably add condition to lock if configured - either by engine-setup, or if the existing code trying to recognize a configured 3.2/3.3 dwh/reports found them.
Probably related to bug #1310421
Can you confirm comment 1?
(In reply to Yaniv Dary from comment #2) > Can you confirm comment 1? It's likely correct, but still might require its own patch, so can't close duplicate, because in existing setups we might want to remove the versionlock.
oVirt 4.0 Alpha has been released, moving to oVirt 4.0 Beta target.
(In reply to Yedidyah Bar David from comment #0) > Description of problem: > > rhevm-setup-plugins has code to version-lock dwh/reports if found on the > system, even if not configured. It also outputs: [ INFO ] DWH and/or Reports were found on this system. To upgrade them, please run the following commands: # yum install rhevm-dwh-setup # engine-setup We should remove this as well. Most likely all of this file.
I suggest to move this to 4.0, no much point in fixing bug 1360363 if we leave this one.
Plugins for dwh and reports were removed. No reason to versionlock reports as they do not exist anymore. Dwh is still versionlocked when installed (as it is prerequisity of dashboard should always be). Sanity on setup/upgrade where done for verification as this seems like CodeChange. If you believe this needs any further verification feel free to reopen.