Bug 755652

Summary: Problem with kickstart from HP iLO3 virtual drive redirection.
Product: Red Hat Enterprise Linux 6 Reporter: Dusty Mabe <dustymabe>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.0CC: dustymabe
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-07 19:05:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dusty Mabe 2011-11-21 17:33:31 UTC
Description of problem:


I am attempting a kickstart install of CentOS 6 using media that is mounted via HP's ilo virtual drive redirection on an HP DL360G7 server. The kickstart file is on the cdrom.

When mounted this way (virtual drive redirection) I always get a dialog box that appears saying it can't find the kickstart file on the cd. It then asks me to specify again where the kickstart file is. Without changing anything I hit ok and it finds the kickstart file on the cdrom the second try. 

This is happening because the virtual drive is not quite ready yet when the getDevices(DEVICE_CDROM) function is run within kickstartFromCD() which is a part of the cdinstall.c file. If I add a sleep(5) right in front of the call to getDevices(DEVICE_CDROM) then the install is 100% non-interactive.


Can we work on getting a fix to this into anaconda? sleep(5) works, but might not be the best solution.


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

anaconda-13.21.82-1.el6.centos.1.x86_64.rpm

How reproducible:

Always


Steps to Reproduce:
1.Build Media with custom kickstart embedded on cdrom
2.Mount the media using virtual drive redirection functionality of HP iLO3. 
3.Start install.
4. Observe that the install prompts user for location of kickstart. 
  
Actual results:

Install prompts user for locations of kickstart. 

Expected results:

Completely non-interactive install. 

Additional info:

This only seems to happen on iLO3 (the specific hardware does not seem to matter). It was a problem in RHEL 5 as well.

Comment 2 RHEL Program Management 2011-12-07 19:05:16 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

Comment 3 Dusty Mabe 2012-01-26 19:41:37 UTC
Note: I have found the following page which documents the same problem. 

http://fedoraproject.org/wiki/Anaconda/NetworkIssues#hp_ILO_CDROM