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.
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 ***