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:
A system run from an OS image does not have a way to automatically use system.devices. When an image is first run, steps need to be introduced to run vgimportdevices or lvmdevices --adddev, but image builders/users have not managed to do this (and images are being configured with use_devicesfile=0 to work around it.) This RFE is to make lvm automatically generate a system.devices file for the root VG when the system is first booted. Two similar methods to do this are:
create_devicesfile_cmdline
--------------------------
Generate /etc/lvm/devices/system.devices from the first devices seen by the system that contain metadata matching the VG/LV in /proc/cmdline.
. lvm.conf use_devicesfile = 1
. lvm.conf create_devicesfile_cmdline = 1 (Or the existence of the empty file /etc/lvm/create_devicesfile_cmdline if it's simpler for image preparation to inject an empty file into an image rather than edit lvm.conf)
. create_devicesfile_cmdline is only used if system.devices does not exist, so it only has an effect on the first boot (and the setting does not need to be disabled after it's run.)
. When devices appear during system startup, pvscan is run on them by the lvm udev rule.
. If system.devices exists, pvscan ignores the device if it's not included in system.devices.
. If system.devices does not exist, pvscan uses the PV if it contains metadata matching /proc/cmdline VG/LV (i.e. rd.lvm.lv=vg/lv)
. vgchange -aay <vgname> is run by the udev rule to activate the root VG. This command recognizes create_devicesfile_cmdline and creates a system.devices file containing devices in the root VG.
create_devicesfile_vg
---------------------
Generate /etc/lvm/devices/system.devices from the first devices seen by the system that contain metadata matching a specified VG name. This would cover cases where the kernel command line doesn't contain VG/LV info.
. lvm.conf use_devicesfile = 1
. lvm.conf create_devicesfile_vg=<vgname> (Or the existence of a file /etc/lvm/create_devicesfile_vg containing a VG name, since it may be simpler to inject this file into an image vs editing lvm.conf.)
. create_devicesfile_vg is only used if system.devices does not exist, so it only has an effect on the first boot (and the setting does not need to be disabled after it's run.)
. When devices appear during system startup, pvscan is run on them by the lvm udev rule.
. If system.devices exists, pvscan ignores the device if it's not included in system.devices.
. If system.devices does not exist, pvscan uses the PV if it contains metadata matching the specified VG name.
. vgchange -aay <vgname> is run by the udev rule to activate the root VG. This command recognizes create_devicesfile_vg and creates a system.devices file containing devices in the root VG.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Comment 3RHEL Program Management
2023-09-23 19:20:41 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 4RHEL Program Management
2023-09-23 19:28:10 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.