Hide Forgot
Created attachment 488870 [details] Screenshot of kickstart disk device error requiring user input Description of problem: If external storage(fibre channel) is connected to the server during kickstart, anaconda gives an error and prompts the user for input. This breaks the ability to have unattended kickstart installs. This issue is causing us to delay our use of RHEL 6 because we are dependent on unattended kickstart installs. For us, this is a RHEL6 deployment stopper. Version-Release number of selected component (if applicable): Discovered in RHEL 6.0, and verified still exists in RHEL 6.1 BETA. How reproducible: Perform automated kickstart with fibre channel storage devices mapped and connected. Steps to Reproduce: 1. Connect fibre channel storage 2. Map disk devices to fibre channel adapter 3. Perform automated kickstart with kickstart file set to install onto internal drive, not any external storage. Actual results: Anaconda interrupts kickstart with errors on each external storage device. Error is "Error processing device". This will occur on each external storage disk found, if the user clicks "ignore", or they can click "ignore all" and the kickstart will continue without further interruption. Expected results: Kickstart installs on selected internal disk without error. Additional info: - Anaconda error screen attached. - Kickstart configuration Attached - List of hardware in use:
List of hardware in use(although I have reproduced on several different system types): - Server HP Proliant DL380 G5 - Installing operating system on internal HP Smart Array (cciss) - Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA - External SAN Storage Array: EMC Clarrion configured for ALUA support.
FYI, this issue was originally reported during RHEL 6.0 #653642 which I thought would fix the issue since the fix for that issue was to be in the RHEL 6.1. But this is a separate issue apparently.
Created attachment 488873 [details] abreviated kickstart configuration used when error occurs
OK. See Bugzilla #653642. This error was occuring because due to that bug I was forced to take the ignore disk statement out of the kickstart. Putting this back into the kickstart now tells Anaconda to ignore all disk devices other than the one we are installing onto: ignoredisk --only-use=cciss/c0d0 So, this fixes this issue for out kickstart. If the "error processing device" is expected behavior for anaconda during installs with extra external disks attached then this can be closed.