Bug 2174927 - Allow changing VG system ID with majority of PVs
Summary: Allow changing VG system ID with majority of PVs
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: lvm2
Version: 8.7
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: David Teigland
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On: 2098182
Blocks: 2174911 2066156
TreeView+ depends on / blocked
 
Reported: 2023-03-02 16:36 UTC by David Teigland
Modified: 2023-08-10 15:41 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2098182
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-150498 0 None None None 2023-03-02 16:38:20 UTC

Description David Teigland 2023-03-02 16:36:54 UTC 
+++ This bug was initially created as a clone of Bug #2098182 +++

Description of problem:

It should be possible to do failover of a VG (using LVM-activate) when the VG is missing devices.  Currently, the vgchange command to change the system ID requires all the PVs to be present.  This will likely require the majority of PVs to be present.

This request comes from bug 2066156.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from David Teigland on 2022-10-14 16:45:56 UTC ---

A commit for this exists in devel branch
https://sourceware.org/git/?p=lvm2.git;a=shortlog;h=refs/heads/dev-dct-vgchange-majority

but it's not yet clear that it would be used, e.g. by LVM-activate.
Note You need to log in before you can comment on or make changes to this bug.