Bug 746775

Summary: RHEL 6.3:Documentation needed on booting from a multipath device
Product: Red Hat Enterprise Linux 6 Reporter: Steven J. Levine <slevine>
Component: doc-DM_MultipathAssignee: Steven J. Levine <slevine>
Status: CLOSED NOTABUG QA Contact: ecs-bugs
Severity: low Docs Contact:
Priority: high    
Version: 6.2CC: bmarzins, bmr, bstevens, coughlan, dherrman, dmair, iannis, jha, john, mhideo, tao
Target Milestone: rcKeywords: Documentation, Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 445734 Environment:
Last Closed: 2011-10-24 20:42:44 UTC Type: ---
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: 445734    
Bug Blocks: 668957    

Comment 3 Steven J. Levine 2011-10-19 20:53:52 UTC

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

Comment 4 Steven J. Levine 2011-10-21 18:45:11 UTC
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.

Comment 5 Ben Marzinski 2011-10-24 20:10:29 UTC
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.

Comment 6 Steven J. Levine 2011-10-24 20:42:44 UTC
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.