This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

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.

we need some way in the storage role to do the equivalent of 1. create a VG, passing the --shared option to vgcreate 2. Activate the new VG using vgchange --lock-start <VG> and 3. Create the LV, passing the --activate sy option to lvcreate.  The proposal is to add a new shared: (true|false) option for volumes to abstract this functionality in the storage role.  See https://github.com/linux-system-roles/storage/issues/341

*** Bug 2182502 has been marked as a duplicate of this bug. ***

Is 9.4 a more likely time frame for shared lv support or is 9.3 still the target?

(In reply to Andrew Price from comment #3)
> Is 9.4 a more likely time frame for shared lv support or is 9.3 still the
> target?

not sure - @vtrefny or @japokorn - any idea?

Moving to 9.4 after discussing with Andrew, this will give us more time to test the changes in blivet and libblockdev needed for this feature.

This bug is scheduled for migration to jira. For questions or issues related to the migration, contact me (dlehman).

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.