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 2015587 - "Rebase" lvm2 to upcoming version 2.03.14 or later [CTC1]
Summary: "Rebase" lvm2 to upcoming version 2.03.14 or later [CTC1]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: lvm2
Version: 8.5
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Marian Csontos
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 2033377
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-19 15:24 UTC by Marian Csontos
Modified: 2022-05-10 16:37 UTC (History)
8 users (show)

Fixed In Version: lvm2-2.03.14-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-10 15:22:14 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLUSTERQE-5160 0 None None None 2022-01-13 05:01:49 UTC
Red Hat Issue Tracker CLUSTERQE-5509 0 None None None 2022-03-16 07:01:03 UTC
Red Hat Issue Tracker RHELPLAN-100247 0 None None None 2021-10-19 15:26:19 UTC
Red Hat Product Errata RHBA-2022:2038 0 None None None 2022-05-10 15:22:30 UTC

Description Marian Csontos 2021-10-19 15:24:48 UTC 
Enhancements (same as RHEL9 bug 2015586):

Few minor enhancements

- Device scanning is skipping /dev subdirectories on different filesystems.
- New async-unsafe option for allocation/vdo_write_policy.
- Devices file: --ignorelockingfailure, locking_type = 0, or --nolocking affects devices file locking as well.
- Add --nohints option.
- lvmdevices: allow --deviceidtype with --addpvid (in addition to using with --adddev)

Enhancements (same as seen in 9-beta):

2.03.14:

- New appmachineid option for global/system_id_source
- New log/journal option (and --journal CLI option)
    - array, default empty, allowed: ["command", "output", "debug"]
    - --journal adds to the array
- config: comment all default settings
- pvscan: add options listlvs listvg checkcomplete
- new udev autoactivation
  - MUST disable by default on rhel8, enable on rhel9

2.03.13:

- check obtain_device_list_from_udev does not change (1)
- check external_device_info_source does not change (udev)
- new devices/multipath_wwids_file option
- [3rd party] tools: Add support for "idm" lock type
- archive/backup refactoring - there may be some differences in cmd output
- devices: rework libudev usage.
- Support --poolmetadataspare with vgsplit and vgmerge.
Comment 2 Corey Marthaler 2021-11-11 02:15:18 UTC 
Marking Verified:Tested based on initial cursory regression test results.

kernel-4.18.0-348.4.el8.kpq0    BUILT: Wed Oct 27 15:00:32 CDT 2021
lvm2-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
lvm2-libs-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
lvm2-dbusd-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:48 CDT 2021
lvm2-lockd-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
boom-boot-1.3-2.el8    BUILT: Tue Jun 15 08:24:06 CDT 2021
device-mapper-1.02.181-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
device-mapper-libs-1.02.181-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
device-mapper-event-1.02.181-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
device-mapper-event-libs-1.02.181-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
device-mapper-persistent-data-0.9.0-4.el8    BUILT: Tue Aug 17 10:17:22 CDT 2021
Comment 8 Corey Marthaler 2021-12-16 19:40:13 UTC 
Pulling this bug out of VERIFIED due to the findings of bug 2033377. Further regression testing found what appears to be a regression in the lvm2-2.03.14-1 build.
Comment 13 Corey Marthaler 2022-02-01 16:46:57 UTC 
Moving this rebase bug back to ON_QA since bug 2033377 appears to be a "known behavior change" and not a regression.  We will be marking this VERIFIED once final 8.6 regression testing has finished on the latest userspace and kernel packages.
Comment 16 errata-xmlrpc 2022-05-10 15:22:14 UTC 
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 (lvm2 bug fix and enhancement update), 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/RHBA-2022:2038
Note You need to log in before you can comment on or make changes to this bug.