Bug 1043916

Summary:	reinstall fails with '"lvremove failed for lv_root" when LVM snapshot exists
Product:	Red Hat Enterprise Linux 6	Reporter:	Harald Klein <hklein>
Component:	anaconda	Assignee:	David Lehman <dlehman>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.4	CC:	jstodola, mganisin, sbueno, sreber, tlavigne
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	anaconda-13.21.228-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-14 06:39:52 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:
Bug Blocks:	1056248

Description Harald Klein 2013-12-17 12:53:31 UTC

Description of problem:

When reinstalling a system where a LVM snapshot of the root LV was created, anaconda fails with the error: "lvremove failed for lv_root"

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

RHEL 6.4

How reproducible:

Try to reinstall on system where a snapshot of the root LV exists

Steps to Reproduce:
1. Create snapshot of root LV
2. Attempt to install with anaconda
3. Select the same disk in anaconda and encounter the error

Actual results:

"lvremove failed for lv_root"

Expected results:

no error

Additional info:

It seems like anaconda tries to remove the lv_root before the snapshot. Bug was already raised for Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=975692

Comment 6 Jan Stodola 2014-09-11 07:44:09 UTC

Retested on Snapshot 5 with anaconda-13.21.229-1.el6, LVM snapshot and it's origin were successfully erased and new LVM partitioning was created by anaconda.

Moving to VERIFIED.

Comment 7 errata-xmlrpc 2014-10-14 06:39:52 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1380.html