Bug 1103812

Summary: Update RHEL 5 documentation and solution for problem encountered by customer
Product: Red Hat Satellite 5 Reporter: Umar Nadeem <unadeem>
Component: Docs Proxy Installation GuideAssignee: Dan Macpherson <dmacpher>
Status: CLOSED WONTFIX QA Contact: Dan Macpherson <dmacpher>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 550CC: cperry, cwawak, daobrien, dlackey, fdewaley, unadeem
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
URL: https://c.na7.visual.force.com/apex/Case_View?id=500A000000J4ILs&sfdc.override=1
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-31 04:03:46 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:    
Bug Blocks: 1018166    

Description Umar Nadeem 2014-06-02 15:51:42 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0
Build Identifier: 

Case : 01061978
https://c.na7.visual.force.com/apex/Case_View?id=500A000000J4ILs&sfdc.override=1


The Customer had problems ignoring disks and drivers during kickstart on RHEL 5. There seems to be documentation missing for RHEL 5, as noted by comment #10 in the case :

" For RHEL5, this possibility isn't documented as being available, the closest option that can be used with part commands would be --onbiosdisk in the part commands (solution 3 only)"

Documentation should be added to RHEL 5.

Also solutions needs to be updated for this problem for RHEL 5, which work for RHEL 6. Here is what could be added to them:

"You use satellite, therefore another possibility is also available : the usage of snippets. If you edit kickstart from the satellite, it is possible to use the %pre section to create a storage.ks file that can be used as a snippet in the partitionning steps."


Reproducible: Always
Comment 4 Umar Nadeem 2014-07-14 14:16:38 UTC 
I have checked documentation for RHEL 6 and RHEL 5 and there seems to be existing information already there. Instead of that, what i am thinking of is a KCS solution regarding "Options for controlling storage access" and outlining the following methods provided in comment 10:

- blacklisting the drivers required to communicate with the san - this is the most direct solution (RHEL 6)
- the ignoredisk command of kickstart (ignoredisk) (RHEL 6)
- edit the kickstart to make it use specific drives (part) (RHEL 6 & RHEL 5)
- the usage of snippets. If you edit kickstart from the satellite, it is possible to use the %pre section to create a storage.ks file that can be used as a snippet in the partitionning steps. (Satellite)