Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
file /usr/lib/systemd/system/blk-availability.service from install of device-mapper-7:1.02.107-5.el7.x86_64 conflicts with file from package lvm2-7:2.02.105-14.el7.x86_64
Description of problem:
On centos-7 , sudo yum install libguestfs-tools fails with conflict errors
Version-Release number of selected component (if applicable):
libguestfs-tools noarch 1:1.28.1-1.55.el7.centos base 108 k
$ uname -a
Linux . 3.10.0-229.20.1.el7.x86_64 #1 SMP Tue Nov 3 19:10:07 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
How reproducible:
everytime i hit this error
Steps to Reproduce:
1.yum install libguestfs-tools
2.
3.
Actual results:
Transaction check error:
file /usr/lib/systemd/system/blk-availability.service from install of device-mapper-7:1.02.107-5.el7.x86_64 conflicts with file from package lvm2-7:2.02.105-14.el7.x86_64
file /usr/sbin/blkdeactivate from install of device-mapper-7:1.02.107-5.el7.x86_64 conflicts with file from package lvm2-7:2.02.105-14.el7.x86_64
file /usr/share/man/man8/blkdeactivate.8.gz from install of device-mapper-7:1.02.107-5.el7.x86_64 conflicts with file from package lvm2-7:2.02.105-14.el7.x86_64
Error Summary
-------------
Expected results:
there should be no error.
Additional info:
(In reply to Lakshmipathi from comment #0)
> Transaction check error:
> file /usr/lib/systemd/system/blk-availability.service from install of
> device-mapper-7:1.02.107-5.el7.x86_64 conflicts with file from package
> lvm2-7:2.02.105-14.el7.x86_64
> file /usr/sbin/blkdeactivate from install of
> device-mapper-7:1.02.107-5.el7.x86_64 conflicts with file from package
> lvm2-7:2.02.105-14.el7.x86_64
> file /usr/share/man/man8/blkdeactivate.8.gz from install of
> device-mapper-7:1.02.107-5.el7.x86_64 conflicts with file from package
> lvm2-7:2.02.105-14.el7.x86_64
We've moved the blkdeactivate script and associated files from lvm2 to device-mapper package in RHEL 7.2 version of lvm2. The bug here is that if device-mapper *alone* is updated and not togethe with lvm2, then we end up with older lvm2 and newer device-mapper package and both having the blkdeactivate, hence the rpm transaction error.
This doesn't happen the other way round if lvm2 is updated first which brings in the newer device-mapper first - there's a proper dep here.
I need to add a condition to the device-mapper package's spec file to conflict with the older lvm2 (or something better if there's a way) so this situation as described here in this report does not happen.
For now, just update lvm2 package first, then everything should be working again.
Comment 3Richard W.M. Jones
2016-01-06 13:26:13 UTC
libguestfs Requires lvm2, but I think because it doesn't
require a specific version of lvm2, yum doesn't think it needs
to be upgraded. Possibly something else (kernel?) is requiring
a newer version of device-mapper, so yum thinks it can satisfy
the libguestfs install just by upgrading device-mapper.
As Peter says, the workaround is to 'yum upgrade lvm2' first.