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.

*** This bug has been marked as a duplicate of bug 623450 ***

Re-opening this - On looking at it again I see it's not a duplicate of  Bug 623450, it's a duplicate of Bug 445734, but for RHEL 6 (Bug 445734 is for RHEL 5). 

However, Bug 445734 is currently in an uncertain state -- it's not clear we can even provide the requested procedure and have it work.. So when that bug gets resolved I'll resolve this one as well.

Early boot works completely different on RHEL5 than on RHEL6.  I have used the documented RHEL6 procedure multiple times to switch root and boot to a multipath device. Or are you asking how to setup multipathing during installation through anaconda? I thought that was already documented in the anaconda documentation.

In my opinion, this is either an anaconda documentation bug, or a duplicate of 623450.  At any rate, it has nothing to do with the RHEL 5 issues in 445734.

Ok, I opened this bug myself as a clone of 445734, thinking that if there was a procedure we were adding to RHEL 5 I also needed to add it to RHEL 6. But if the issues of that bug do not apply to RHEL 6 (or are addressed in 623450) then it's not a bug.