Red Hat Bugzilla – Bug 1609175
[downstream clone - 4.2.6] ovirt-web-ui is not getting updating during engine-setup which is creating unexpected results
Last modified: 2018-09-04 09:42:30 EDT
+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1599525 +++ ====================================================================== Description of problem: Currently, the ovirt-web-ui is not getting updated during engine-setup. So if a user upgrades the RHV-M from 4.1 to 4.2, the ovirt-web-ui package will be still from 4.1. The server was upgraded successfully to 4.2 but ovirt-web-ui is not upgraded. rpm -qa|egrep -i "rhvm|web-ui" rhvm-doc-4.2.5-1.el7ev.noarch rhvm-4.2.4.5-0.1.el7_3.noarch ovirt-web-ui-1.2.1-1.el7ev.noarch rhvm-setup-plugins-4.2.9-1.el7ev.noarch rhvm-dependencies-4.2.1-1.el7ev.noarch rhvm-branding-rhv-4.2.3-1.el7ev.noarch Because of 4.1 ovirt-web-ui and 4.2 manager, the customer was seeing all the VMs in the user portal although the user doesn't have permission to see these users. This was resolved after he upgraded the ovirt-web-ui manually. Version-Release number of selected component (if applicable): RHV 4.2.4 How reproducible: 100% Steps to Reproduce: 1. Upgrade RHV-M from 4.1 to 4.2. 2. The ovirt-web-ui is not getting updated and has to update manually. Actual results: ovirt-web-ui not getting updated during engine-setup Expected results: Additional info: (Originally by Nijin Ashok)
we would add it to the list of packages updated by engine-setup. No need to lock/hide it really, but updating it as part of regular engine upgrade as makes sense. Didi, where exactly it should be added? (Originally by michal.skrivanek)
(In reply to Michal Skrivanek from comment #1) > we would add it to the list of packages updated by engine-setup. No need to > lock/hide it really, but updating it as part of regular engine upgrade as > makes sense. > Didi, where exactly it should be added? In packaging/setup/ovirt_engine_setup/engine/constants.py : DEFAULT_ADDITIONAL_PACKAGES . (Originally by didi)
Please note that you now just require it, by the engine, without any version. Is a new version compatible with an old engine? If not, this will fail: 1. Install and setup old engine (say, 4.1) 2. Add newer repo/channel (say, 4.2) 3. yum update (but do not run engine-setup) 4. restart engine? If you want to prevent that, either require/conflict with specific versions, or add also to versionlock. Or both. (Originally by didi)
It is compatible, it’s just outdated when people only use engine-setup and not do full yum update (Originally by michal.skrivanek)
engine-setup updated package ovirt-web-ui 1.2.1 to 1.3.9 successfully verified in ovirt-engine-4.2.6-0.1.el7ev.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2623