Back to bug 1325394

Who When What Removed Added
Alasdair Kergon 2016-04-08 18:11:47 UTC Assignee lvm-team prajnoha
Vivek Goyal 2016-04-11 12:19:50 UTC CC sdodson
Peter Rajnoha 2016-04-11 13:11:20 UTC Status NEW POST
Scott Dodson 2016-04-11 13:12:16 UTC CC dron
Peter Rajnoha 2016-05-04 13:39:47 UTC Depends On 1332990
Fixed In Version lvm2-2.02.152-1.el7
Peter Rajnoha 2016-05-04 14:01:46 UTC Status POST MODIFIED
Fixed In Version lvm2-2.02.152-1.el7 lvm2-2.02.152-2.el7
Roman Bednář 2016-05-04 14:20:36 UTC CC rbednar
errata-xmlrpc 2016-05-05 07:10:37 UTC Status MODIFIED ON_QA
Peter Rajnoha 2016-06-02 12:58:21 UTC Blocks 1295577, 1313485
CC lakshmipathi.g
Peter Rajnoha 2016-06-03 10:01:04 UTC CC jpazdziora
Peter Rajnoha 2016-08-15 09:30:23 UTC Doc Text Cause:
There was an incorrectly defined dependency between lvm2-libs and device-mapper-event LVM2 subpackages prior to lvm2 version 2.02.111. Also, blkdeactivate script and blk-availability.service file was moved from lvm2 to device-mapper subpackage.

Consequence:
When updating only device-mapper subpackages, without updating lvm2 package, we ended up with a file conflict for blkdeactivate and blk-availability.service files as they were included in both lvm2 and device-mapper packages.

Fix:
LVM2 and related device-mapper subpackages have fixed dependencies since LVM2 version 2.02.111. To avoid problems when updating from older versions of LVM2 packages and its subpackages, there's direct conflict defined explicitly in the packages now.

Result:
It's not possible to install old device-mapper packages with newer lvm2 packages - the packaging infrastructure will issue an error, giving an information about the version required to resolve the conflict.
Peter Rajnoha 2016-08-15 10:13:34 UTC Doc Text Cause:
There was an incorrectly defined dependency between lvm2-libs and device-mapper-event LVM2 subpackages prior to lvm2 version 2.02.111. Also, blkdeactivate script and blk-availability.service file was moved from lvm2 to device-mapper subpackage.

Consequence:
When updating only device-mapper subpackages, without updating lvm2 package, we ended up with a file conflict for blkdeactivate and blk-availability.service files as they were included in both lvm2 and device-mapper packages.

Fix:
LVM2 and related device-mapper subpackages have fixed dependencies since LVM2 version 2.02.111. To avoid problems when updating from older versions of LVM2 packages and its subpackages, there's direct conflict defined explicitly in the packages now.

Result:
It's not possible to install old device-mapper packages with newer lvm2 packages - the packaging infrastructure will issue an error, giving an information about the version required to resolve the conflict.
There was an incorrectly defined dependency between lvm2-libs and device-mapper-event LVM2 subpackages prior to lvm2 version 2.02.111. When updating only device-mapper subpackages, without updating lvm2 package, we may have ended up with file conflicts if files were moved around subpackages. These dependencies are fixed since LVM2 version 2.02.111. To avoid problems when updating from older versions, there's direct conflict defined explicitly in the packages now which, if hit, will give an information about the minimum required version to resolve this conflict.
Roman Bednář 2016-09-21 12:04:35 UTC Status ON_QA VERIFIED
errata-xmlrpc 2016-11-02 12:15:01 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-11-04 04:20:02 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-11-04 00:20:02 UTC
Pavel Najman 2021-09-03 12:38:00 UTC Pool ID sst_platform_storage_rhel_7 sst_logical_storage_rhel_7

Back to bug 1325394