Bug 88407

Summary: kickstart won't install swap on mirror md
Product: [Retired] Red Hat Linux Reporter: jmccann
Component: anacondaAssignee: Michael Fulbright <msf>
Status: CLOSED NOTABUG QA Contact: Mike McLean <mikem>
Severity: high Docs Contact:
Priority: medium    
Version: 9CC: cschalle
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-04-11 17:03:15 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 configuration used none

Description jmccann 2003-04-09 21:49:59 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030401

Description of problem:
It seems that kickstart won't install swap on a RAID1 metadevice.

The installer says something like "need two devices for mirror" and then reboots.

I got this error message with 8.0 too but it continued with the install.

A fault tolerant system should have swap on a mirror.

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


How reproducible:
Always

Steps to Reproduce:
1. install swap on a RAID1 device during KS
2. 
3.
    

Actual Results:  reboots

Expected Results:  Works.

Additional info:

Comment 1 jmccann 2003-04-09 21:51:20 UTC
Created attachment 91049 [details]
Kickstart configuration used

Sensitive information has been removed fron ks.cfg.

Comment 2 Michael Fulbright 2003-04-11 17:03:15 UTC
You need to specify a mount point of 'swap', ie:

  raid --level=1 --device=md0 --fstype swap raid.01 raid.02

should be:

  raid swap --level=1 --device=md0 --fstype swap raid.01 raid.02

I'll add some sanity checking for the mount point when we parse the ks.cfg.

Comment 3 jmccann 2003-04-11 17:22:03 UTC
Sorry to comment on a closed bug.  Thanks for the fix!  However, the ks.cfg file
came directly from redhat-config-kickstart.  So, maybe that has a bug?