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.
Bug 1342441 - Attempt to upgrade device-mapper from RHEL 7.0 to 7.2 version fails with lvm2 conflict
Summary: Attempt to upgrade device-mapper from RHEL 7.0 to 7.2 version fails with lvm2...
Keywords:
Status: CLOSED DUPLICATE of bug 1325394
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: LVM and device-mapper development team
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-03 09:42 UTC by Jan Pazdziora
Modified: 2021-09-03 12:40 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-03 10:01:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Pazdziora 2016-06-03 09:42:33 UTC
Description of problem:

Having RHEL 7.0 and attempting to install some software that requires newer version of device-mapper, the upgrade of device-mapper package fails.

Version-Release number of selected component (if applicable):

lvm2-2.02.105-14.el7.x86_64
device-mapper-1.02.84-14.el7.x86_64

upgrading to

device-mapper-1.02.107-5.el7_2.2.x86_64

How reproducible:

Deterministic.

Steps to Reproduce:
1. Have RHEL 7.0, subscribed to CDN.
2. Run yum upgrade --disablerepo='*-rpms' --enablerepo=rhel-7-server-rpms -y device-mapper

Actual results:

# yum upgrade --disablerepo='*-rpms' --enablerepo=rhel-7-server-rpms -y device-mapper
Loaded plugins: product-id, subscription-manager
rhel-7-server-rpms                                       | 3.7 kB     00:00     
rhel-7-server-rpms/7Server/x86_64/primary_db               |  21 MB   00:02     
(1/2): rhel-7-server-rpms/7Server/x86_64/group_gz          | 134 kB   00:00     
(2/2): rhel-7-server-rpms/7Server/x86_64/updateinfo        | 1.2 MB   00:01     
Resolving Dependencies
--> Running transaction check
---> Package device-mapper.x86_64 7:1.02.84-14.el7 will be updated
--> Processing Dependency: device-mapper = 7:1.02.84-14.el7 for package: 7:device-mapper-event-1.02.84-14.el7.x86_64
--> Processing Dependency: device-mapper = 7:1.02.84-14.el7 for package: 7:device-mapper-libs-1.02.84-14.el7.x86_64
---> Package device-mapper.x86_64 7:1.02.107-5.el7_2.2 will be an update
--> Running transaction check
---> Package device-mapper-event.x86_64 7:1.02.84-14.el7 will be updated
---> Package device-mapper-event.x86_64 7:1.02.107-5.el7_2.2 will be an update
--> Processing Dependency: device-mapper-event-libs = 7:1.02.107-5.el7_2.2 for package: 7:device-mapper-event-1.02.107-5.el7_2.2.x86_64
---> Package device-mapper-libs.x86_64 7:1.02.84-14.el7 will be updated
---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7_2.2 will be an update
--> Running transaction check
---> Package device-mapper-event-libs.x86_64 7:1.02.84-14.el7 will be updated
---> Package device-mapper-event-libs.x86_64 7:1.02.107-5.el7_2.2 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package                  Arch   Version               Repository          Size
================================================================================
Updating:
 device-mapper            x86_64 7:1.02.107-5.el7_2.2  rhel-7-server-rpms 252 k
Updating for dependencies:
 device-mapper-event      x86_64 7:1.02.107-5.el7_2.2  rhel-7-server-rpms 167 k
 device-mapper-event-libs x86_64 7:1.02.107-5.el7_2.2  rhel-7-server-rpms 169 k
 device-mapper-libs       x86_64 7:1.02.107-5.el7_2.2  rhel-7-server-rpms 305 k

Transaction Summary
================================================================================
Upgrade  1 Package (+3 Dependent packages)

Total download size: 892 k
Downloading packages:
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
warning: /var/cache/yum/x86_64/7Server/rhel-7-server-rpms/packages/device-mapper-event-1.02.107-5.el7_2.2.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID fd431d51: NOKEY
Public key for device-mapper-event-1.02.107-5.el7_2.2.x86_64.rpm is not installed
(1/4): device-mapper-event-1.02.107-5.el7_2.2.x86_64.rpm   | 167 kB   00:00     
(2/4): device-mapper-1.02.107-5.el7_2.2.x86_64.rpm         | 252 kB   00:00     
(3/4): device-mapper-event-libs-1.02.107-5.el7_2.2.x86_64. | 169 kB   00:00     
(4/4): device-mapper-libs-1.02.107-5.el7_2.2.x86_64.rpm    | 305 kB   00:00     
--------------------------------------------------------------------------------
Total                                              633 kB/s | 892 kB  00:01     
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
Importing GPG key 0xFD431D51:
 Userid     : "Red Hat, Inc. (release key 2) <security>"
 Fingerprint: 567e 347a d004 4ade 55ba 8a5f 199e 2f91 fd43 1d51
 Package    : redhat-release-server-7.0-1.el7.x86_64 (@beaker-Server/7.0)
 From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
Importing GPG key 0x2FA658E0:
 Userid     : "Red Hat, Inc. (auxiliary key) <security>"
 Fingerprint: 43a6 e49c 4a38 f4be 9abf 2a53 4568 9c88 2fa6 58e0
 Package    : redhat-release-server-7.0-1.el7.x86_64 (@beaker-Server/7.0)
 From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
Running transaction check
Running transaction test


Transaction check error:
  file /usr/lib/systemd/system/blk-availability.service from install of device-mapper-7:1.02.107-5.el7_2.2.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_2.2.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_2.2.x86_64 conflicts with file from package lvm2-7:2.02.105-14.el7.x86_64

Error Summary
-------------

Expected results:

No error.

Additional info:

Comment 1 Peter Rajnoha 2016-06-03 10:01:04 UTC
This was a bug in 7.0 lvm2 spec file (and dependency of lvm2-libs subpackage on device-mapper-event subpackage) and at the same time the fact we moved the blkdeactivate script from lvm2 to device-mapper.

This is resolved in 7.1 (lvm2 2.02.115-3) and later versions of lvm2/device-mapper packages and in 7.3 we're adding Conflicts for the older lvm2-libs so you'll there's now better error message when upgrading from 7.0 to 7.3 which will tell you that you need to upgrade lvm2 as well.

If you do upgrade from 7.0 to 7.2, you have to upgrade lvm2 together with device-mapper so this inconsistency fades away.

(This was already reported as bug #1294128 and bug #1325394)

*** This bug has been marked as a duplicate of bug 1325394 ***


Note You need to log in before you can comment on or make changes to this bug.