Bug 253888

Summary: Anaconda Kickstart doesn't see zFCP devices (sda)
Product: Red Hat Enterprise Linux 5 Reporter: Arlinton Bourne <abourne>
Component: anacondaAssignee: David Cantrell <dcantrell>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: low    
Version: 5.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-08-23 17:46:48 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:
Attachments:
Description Flags
Kickstart zFCP none

Description Arlinton Bourne 2007-08-22 17:31:07 UTC 
Description of problem:
Within the kickstart file for a RHEL5 s390x install. 
Using the keyword zFCP and it's options sets up my FCP drives. They come up as
sda and sdb. Alas when trying to partition them using the part commands anaconda
whines and quits essentially complaining that at kickstart line X nonexistant
drive sda.
The kickstart line looks like:
part raid.30 --size=100 --grow --ondisk=sda
part raid.31 --size=100 --grow --ondisk=sdb

Also I'm passing proper FCP_x  arguments via zVM.

I've tried initiating the zFCP drive manually in my pre script.
It does the same stuff.

The installation works file w/o kickstart.


Version-Release number of selected component (if applicable):
RHEL 5 GOLD INSTALL

How reproducible:
100%
Comment 1 David Cantrell 2007-08-22 17:43:53 UTC 
Is this happening with a 5.1 tree?  Nightly or beta.
Comment 2 Arlinton Bourne 2007-08-22 19:42:20 UTC 
I haven't tried this with a 5.1 tree as yet. Should I?
Also I've found out that the: 

clearpart --all --initlabel 

seems not to work as well.
While DASDs are get formatted by dasdfmt the zFCP devices do not get
(re)initialized and still have information on them.

I deducted this by creating a md1 device out of the zFCP devices when i
installed RHEL and adding it to VolGroup00, extending the root lv (LogVol00),
expanding the ext3 fs then kicking off a fresh install (manually).

Next thing I'll attach is the kickstart file.
Comment 3 David Cantrell 2007-08-22 19:46:11 UTC 
Yeah, please do testing with 5.1 trees now.  We're so near the release and so
much work has gone in to 5.1 now.
Comment 4 Arlinton Bourne 2007-08-23 17:35:24 UTC 
Created attachment 171256 [details]
Kickstart zFCP

It works well on the 20070822.1 tree
Just fails badly on 5.0 Gold

Here is the kickstart file.