Bug 2174927

Summary: Allow changing VG system ID with majority of PVs
Product: Red Hat Enterprise Linux 8 Reporter: David Teigland <teigland>
Component: lvm2Assignee: David Teigland <teigland>
lvm2 sub component: Command-line tools QA Contact: cluster-qe <cluster-qe>
Status: ASSIGNED --- Docs Contact:
Severity: medium    
Priority: high CC: agk, heinzm, jbrassow, msnitzer, prajnoha, thornber, zkabelac
Version: 8.7Keywords: Triaged
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2098182 Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2098182    
Bug Blocks: 2174911, 2066156    

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.