Red Hat Bugzilla – Bug 1418166
Remove dependencies required by spice on ppc64le
Last modified: 2017-08-01 23:17:22 EDT
Description of problem: In qemu-kvm-rhev based on 2.6 we introduce two install dependencies used by spice functionality: - usbredir (direct Requires) - libcacard (indirect by BuildRequires) These packages are shipped in Optional channel on ppc64le so we are not able to install qemu-kvm-rhev in case Optional channel is unavailable. We need to properly handle this dependencies to not break ppc64le installation.
Fix included in qemu-kvm-rhev-2.8.0-4.el7
Verified that qemu-kvm-rhev-2.8.0-3 required the dependency of usbredir and libcacard while qemu-kvm-rhev-2.9.0-3 doesn't. On a fresh installed host with only a small set packages installed and without usbredir and libcacard: On qemu-kvm-rhev-2.8.0-3.el7.ppc64le: # rpm -ivh qemu-kvm-rhev-2.8.0-3/* error: Failed dependencies: libiscsi.so.2()(64bit) is needed by qemu-img-rhev-10:2.8.0-3.el7.ppc64le libtcmalloc.so.4()(64bit) is needed by qemu-img-rhev-10:2.8.0-3.el7.ppc64le libtcmalloc.so.4()(64bit) is needed by qemu-kvm-common-rhev-10:2.8.0-3.el7.ppc64le SLOF >= 20160223-1.gitdbbfda4 is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le ipxe-roms-qemu >= 20160127-4 is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le libcacard.so.0()(64bit) is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le libfdt.so.1()(64bit) is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le libfdt.so.1(LIBFDT_1.2)(64bit) is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le libibverbs.so.1()(64bit) is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le libibverbs.so.1(IBVERBS_1.0)(64bit) is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le libibverbs.so.1(IBVERBS_1.1)(64bit) is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le libiscsi.so.2()(64bit) is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le libpulse.so.0()(64bit) is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le libpulse.so.0(PULSE_0)(64bit) is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le librdmacm.so.1()(64bit) is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le librdmacm.so.1(RDMACM_1.0)(64bit) is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le libtcmalloc.so.4()(64bit) is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le seavgabios-bin >= 1.9.1-4 is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le usbredir >= 0.7.1 is needed by qemu-kvm-rhev-10:2.8.0-3.el7.ppc64le On qemu-kvm-rhev-2.9.0-3.el7.ppc64le: # rpm -ivh qemu-kvm-rhev-2.9.0-3/* error: Failed dependencies: libiscsi.so.2()(64bit) is needed by qemu-img-rhev-10:2.9.0-3.el7.ppc64le libtcmalloc.so.4()(64bit) is needed by qemu-img-rhev-10:2.9.0-3.el7.ppc64le libtcmalloc.so.4()(64bit) is needed by qemu-kvm-common-rhev-10:2.9.0-3.el7.ppc64le SLOF >= 20170303-1.git66d250e is needed by qemu-kvm-rhev-10:2.9.0-3.el7.ppc64le ipxe-roms-qemu >= 20170123-1 is needed by qemu-kvm-rhev-10:2.9.0-3.el7.ppc64le libfdt.so.1()(64bit) is needed by qemu-kvm-rhev-10:2.9.0-3.el7.ppc64le libfdt.so.1(LIBFDT_1.2)(64bit) is needed by qemu-kvm-rhev-10:2.9.0-3.el7.ppc64le libibverbs.so.1()(64bit) is needed by qemu-kvm-rhev-10:2.9.0-3.el7.ppc64le libibverbs.so.1(IBVERBS_1.0)(64bit) is needed by qemu-kvm-rhev-10:2.9.0-3.el7.ppc64le libibverbs.so.1(IBVERBS_1.1)(64bit) is needed by qemu-kvm-rhev-10:2.9.0-3.el7.ppc64le libiscsi.so.2()(64bit) is needed by qemu-kvm-rhev-10:2.9.0-3.el7.ppc64le libpulse.so.0()(64bit) is needed by qemu-kvm-rhev-10:2.9.0-3.el7.ppc64le libpulse.so.0(PULSE_0)(64bit) is needed by qemu-kvm-rhev-10:2.9.0-3.el7.ppc64le librdmacm.so.1()(64bit) is needed by qemu-kvm-rhev-10:2.9.0-3.el7.ppc64le librdmacm.so.1(RDMACM_1.0)(64bit) is needed by qemu-kvm-rhev-10:2.9.0-3.el7.ppc64le libtcmalloc.so.4()(64bit) is needed by qemu-kvm-rhev-10:2.9.0-3.el7.ppc64le seavgabios-bin >= 1.10.2-1 is needed by qemu-kvm-rhev-10:2.9.0-3.el7.ppc64le usbredir and libcacard dependencies are removed and yum install qemu-kvm-rhev successfully without the two spice related packages. So, the bug is fixed.
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/RHSA-2017:2392