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.
Description of problem:
The lvm.conf in initramfs contains a number of settings that are no longer used. We should discuss any lvm.conf changes you have needed to make in the past and decide if they can be dropped completely, or replaced with something different.
I'm not sure where the base file is coming from, but there are a number of settings (both commented and not) that are no longer used and no longer output from lvmconfig --type default, so once the base file is refreshed (from lvmconfig --type default --withcomments) a number of obsolete entries should disappear.
Some more specific comments on a few intentional changes I see:
1. locking_type. This setting is no longer used, I think you used it previously to tell lvm to avoid using file locks on the readonly fs. This should be replaced with a command line option like --nolocking which is the simplest.
There's a complex mess of other options similar to nolocking that have been added over the years if there are some particular restrictions you want to apply to the command. I can describe these if you are interested.
2. use_lvmetad: lvmetad no longer exists, and this setting doesn't do anything.
3. Do not run lvmetad update via pvscan in udev rule - lvmetad is not running yet in dracut!
There's no more lvmetad, and I'm not entirely sure about the changes to 69-dm-lvm-metad.rules (which will be replaced by lvm-activation.rules). If you were trying to avoid running the pvscan command entirely, then similar editing of the rule would be needed. If you are intending to disable autoactivation, that is done by setting auto_activation_volume_list=[]. But maybe I'm not understanding the main issue this is trying to avoid.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Comment 4RHEL Program Management
2021-02-01 07:31:09 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.