Bug 1331889 - Review mechanism for wiping of metadata device when creating raid volumes
Summary: Review mechanism for wiping of metadata device when creating raid volumes
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: 2.02.152
Hardware: All
OS: All
low
low
Target Milestone: ---
: ---
Assignee: Heinz Mauelshagen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1330933
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-29 23:34 UTC by Alasdair Kergon
Modified: 2019-11-11 16:51 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-11 16:51:56 UTC
rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.