Description of problem: The vdsm sos plugin moved from vdsm to sos without reflecting this change in the rpm dependencies, so installation of the latest vdsm (4.3) fails on conflicting files in /usr/lib/python2.7/site-packages/sos/plugins/vdsm.py* Version-Release number of selected component (if applicable): sos-3.7-3.el7.noarch vdsm-4.30.16-3.el7ev How reproducible: Always Steps to Reproduce: 1. Install vdsm on a 7.7 machine Actual results: yum fails to install vdsm because of conflicting files Expected results: yum should install vdsm successfully
Re-Sync with Jira
reopening. This needs to be resolved differently for POWER arch where we have to stay at 7.6.
Wouldn't it be nicer to create a new subpackage for vdsm that just installs the sos plugin (vdsm-sos) and have the new sos conflicts on that that package with vdsm "recommends" vdsm-sos ?
(In reply to Yuval Turgeman from comment #4) > Wouldn't it be nicer to create a new subpackage for vdsm that just installs > the sos plugin (vdsm-sos) and have the new sos conflicts on that that > package with vdsm "recommends" vdsm-sos ? At the moment sos in RHEL 7.7 is frozen, we can't do any changes there. So right now sos-3.7-4.el7, which is part of RHEL 7.7 contains this spec option to handle conflicts with current vdsm: Conflicts: vdsm <= 4.30.17 So to stay consistent I think we just need to include the plugin in 4.3 VDSM only for power architecture. We don't need to do anything on master, because 4.4 VDSM will be available only on RHEL 8.1, which already contains sos with VDSM plugin.
Verified on vdsm-4.30.22-1.el7ev.x86_64 Regular RHEL 7.7 and P9 with RHEL 7.6
This is not a bug in VDSM, but in ovirt-log collector: $ rpm -qp --requires vdsm-4.30.22-1.el7ev.ppc64le.rpm | grep sos sos $ rpm -qp --requires vdsm-4.30.22-1.el7ev.x86_64.rpm | grep sos sos >= 3.7-3 According to above we have a problem in ovirt-log-collector: Error: Package: ovirt-log-collector-4.3.3-1.el7ev.noarch (rhv-4.3.5) Requires: sos >= 3.7 Installed: sos-3.6-9.el7.noarch (@anaconda/7.6) sos = 3.6-9.el7 Available: sos-3.0-23.el7.noarch (base-production-mirror) sos = 3.0-23.el7 Available: sos-3.0-23.el7_0.4.noarch (base-production-mirror) sos = 3.0-23.el7_0.4 Available: sos-3.0-23.el7_0.11.noarch (base-production-mirror) sos = 3.0-23.el7_0.11 Available: sos-3.2-15.el7.noarch (base-production-mirror) sos = 3.2-15.el7 Available: sos-3.2-15.el7_1.1.noarch (base-production-mirror) sos = 3.2-15.el7_1.1 Available: sos-3.2-15.el7_1.5.noarch (base-production-mirror) sos = 3.2-15.el7_1.5 Available: sos-3.2-15.el7_1.8.noarch (base-production-mirror) sos = 3.2-15.el7_1.8 Available: sos-3.2-35.el7.noarch (base-production-mirror) sos = 3.2-35.el7 Available: sos-3.2-35.el7_2.3.noarch (base-production-mirror) sos = 3.2-35.el7_2.3 Available: sos-3.3-4.el7.noarch (base-production-mirror) sos = 3.3-4.el7 Available: sos-3.3-5.el7_3.noarch (base-production-mirror) sos = 3.3-5.el7_3 Available: sos-3.4-5.el7.noarch (base-production-mirror) sos = 3.4-5.el7 Available: sos-3.4-6.el7.noarch (base-production-mirror) sos = 3.4-6.el7 Available: sos-3.4-13.el7_4.noarch (base-production-mirror) sos = 3.4-13.el7_4 Available: sos-3.5-6.el7.noarch (base-production-mirror) sos = 3.5-6.el7 Available: sos-3.5-7.el7_5.noarch (base-production-mirror) sos = 3.5-7.el7_5 Available: sos-3.5-9.el7_5.noarch (base-production-mirror) sos = 3.5-9.el7_5 Available: sos-3.6-11.el7_6.noarch (base-production-mirror) sos = 3.6-11.el7_6 Available: sos-3.6-13.el7_6.noarch (base-production-mirror) sos = 3.6-13.el7_6 Available: sos-3.6-16.el7_6.noarch (base-production-mirror) sos = 3.6-16.el7_6 Available: sos-3.6-17.el7_6.noarch (base-internal-compose) sos = 3.6-17.el7_6 Created BZ1729117 to cover sos-log-collector issue
log-collector is not published for power 9 so not an issue.
Maybe I interpreted badly Comment 11, is this error happening on host or engine? According to Sandro it cannot happen on host, as ovirt-log-collector is not available on host. So if it happens only on engine, than there is an error in QE verification, because engine 4.3.5 should also be used only with RHEL 7.7
You are right Martin, the problem with ovirt-log-collector appears only on engine. Hosts don not install it.
As per engine on P9 is no longer supported, moving this to verified.
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-2019:2432