RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

I've got a /dev/sd[a-c].  In that I have a partition on sdb and sdc which are raided as /dev/md0 and mounted on my /boot.  Anaconda was attempting to install the boot loader on /dev/sdb instead of /dev/md0

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

Whatever version comes with the RHEL6 beta 2 that launched today.

How reproducible:

Only tested once so far.

Steps to Reproduce:
1.  Create /dev/sdb1 and /dev/sdc1
2.  Software raid them (raid1) at /boot ext4
3.  click next to the boot loader screen.
  
Actual results:

"Install boot loader on /dev/sdb" was displayed

Expected results:

"Install boot loader on /dev/md0"

Additional info:

This was done with a kickstart install but we had the storage section blank so we could do that manually.

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.

Nope, looks like what I thought would work does in fact not work.  The behavior it's showing seems to be correct.