Bug 1331889

Summary: Review mechanism for wiping of metadata device when creating raid volumes
Product: [Community] LVM and device-mapper Reporter: Alasdair Kergon <agk>
Component: lvm2Assignee: Heinz Mauelshagen <heinzm>
lvm2 sub component: Mirroring and RAID QA Contact: cluster-qe <cluster-qe>
Status: CLOSED INSUFFICIENT_DATA Docs Contact:
Severity: low    
Priority: low CC: agk, heinzm, jbrassow, msnitzer, prajnoha, zkabelac
Version: 2.02.152Flags: rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-11 16:51:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1330933    
Bug Blocks:    

Description Alasdair Kergon 2016-04-29 23:34:32 UTC
If an activation volume_list is configured, the operation may fail and when it fails, LVs are left behind in states that 'lvremove vg' does not remove.

Reconsider how wiping volumes should interact with volume_list configurations and tags and fix the error paths.

Comment 1 Heinz Mauelshagen 2019-11-11 16:51:56 UTC
The description is not providing an example and related https://bugzilla.redhat.com/1208657 got addressed already.
Closing insufficient data.