Bug 586985

Summary:	Don't clear BIOS RAID member disks
Product:	Red Hat Enterprise Linux 6	Reporter:	David Lehman <dlehman>
Component:	anaconda	Assignee:	Hans de Goede <hdegoede>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0	CC:	alan.ernhart, atodorov, bdwheele, borgan, ckannan, felix.kuehling, frank.arnold, hoffmann, jburke, jstodola, luugi.marsan, mganisin, mgordon, pholica, psplicha, quintela, rdoty, twoerner
Target Milestone:	rc
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:	anaconda_trace_hash:02b1138f15e8a5ac1f6e134bb9afaf4e05a7421d95027b8c1bfbc30735e8fe74
Fixed In Version:	anaconda-13.21.34-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	563526	Environment:
Last Closed:	2010-11-10 19:43:02 UTC	Type:	---
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:	563526
Bug Blocks:	582286

Comment 2 RHEL Program Management 2010-04-28 16:47:11 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Hans de Goede 2010-04-28 19:17:29 UTC

Uhg, this bug will make us try to clear the format (removing metadata) of any BIOS RAID or multipath member disk when clearPartType is CLEARPART_TYPE_ALL.

I've send a patch to the list for review, cloning this for F-13.

Comment 4 Hans de Goede 2010-04-29 08:14:26 UTC

This is fixed in anaconda-13.21.34-1, moving to modified.

Comment 6 David Lehman 2010-05-10 15:52:41 UTC

*** Bug 589224 has been marked as a duplicate of this bug. ***

Comment 9 releng-rhel@redhat.com 2010-11-10 19:43:02 UTC

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.