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.

+++ This bug was initially created as a clone of Bug #1196580 +++

Description of problem:

There has been a long standing discussion on the behavior of vgchange in a cluster in regard to exclusive activation of volumes. From the user/admin perspective it makes more sense to have the command unambiguously do what a user may expect, and not end up having random results sometimes. 
This has been reported a few times in bugs #677817 and later in #1191724
In the former it was at some point fixed to work as one would expect, but it is no longer the case even in RHEL6 (so in RHEL6 it could be considered a regression as well).

So in short, we would benefit greatly of making vgchange more unambiguous by adding an option to LOCALLY activate LVs in a VG, in exclusive mode by supplying something like:


vgchange -aley vg_name


The command should return with an exit code of 1 (error out) if it cannot execute what the user demands due to some (or all) of LVs belonging to this VG being already active (or exclusively active) on another node. It should only return an exit code of 0 (success) if all LVs belonging to the VG in question are successfully locally activated.

Let's move this to RHEL7 to concentrate on bug fixing in RHEL6, not adding new features. Also, customers not haven't asked for this in RHEL6 yet.

*** This bug has been marked as a duplicate of bug 1196580 ***