Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 586985 - Don't clear BIOS RAID member disks
Don't clear BIOS RAID member disks
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: rc
: ---
Assigned To: Hans de Goede
Release Test Team
: 589224 (view as bug list)
Depends On: 563526
Blocks: 582286
  Show dependency treegraph
Reported: 2010-04-28 11:40 EDT by David Lehman
Modified: 2010-11-10 14:43 EST (History)
18 users (show)

See Also:
Fixed In Version: anaconda-13.21.34-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 563526
Last Closed: 2010-11-10 14:43:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Comment 2 RHEL Product and Program Management 2010-04-28 12:47:11 EDT
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
Comment 3 Hans de Goede 2010-04-28 15:17:29 EDT
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 04:14:26 EDT
This is fixed in anaconda-13.21.34-1, moving to modified.
Comment 6 David Lehman 2010-05-10 11:52:41 EDT
*** Bug 589224 has been marked as a duplicate of this bug. ***
Comment 9 releng-rhel@redhat.com 2010-11-10 14:43:02 EST
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.

Note You need to log in before you can comment on or make changes to this bug.