Bug 159426 - Kickstart '--noformat' Option Non-functional With 'raid' Directive
Kickstart '--noformat' Option Non-functional With 'raid' Directive
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Lumens
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2005-06-02 12:19 EDT by Chris Hollowell
Modified: 2008-08-02 19:40 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-08-24 13:21:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch Which Appears to Correct This Issue (344 bytes, patch)
2005-06-02 12:22 EDT, Chris Hollowell
no flags Details | Diff
Another Patch Which Appears to Resolve This Issue (511 bytes, patch)
2005-06-10 13:28 EDT, Chris Hollowell
no flags Details | Diff

  None (edit)
Description Chris Hollowell 2005-06-02 12:19:25 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Red Hat/1.7.8-

Description of problem:
RHEL3 Kickstart documentation indicates that '--noformat'
may be used with the 'raid' directive to prevent MD devices
from being formatted.  However, issuing 
'raid /data --level 0 --device md0 --noformat' fails on
hosts with known intact level 0 software RAID arrays with
the following error message:
"Unable to locate raid device None to use for /data."
This seems to be due to the fact that the constructor
for the RaidRequestSpec class in partRequests.py is not
setting self.device.  The attached patch appears to fix
the problem.

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

How reproducible:

Steps to Reproduce:
1. Use Kickstart to install a system with an existing software RAID array.
2. Issue a 'raid' directive in your Kickstart configuration with the
   '--noformat' option.

Actual Results:  Anaconda displays an "Unable to locate raid device None" message.

Expected Results:  Anaconda should have found the specified MD device.

Additional info:
Comment 1 Chris Hollowell 2005-06-02 12:22:12 EDT
Created attachment 115093 [details]
Patch Which Appears to Correct This Issue
Comment 2 Jeremy Katz 2005-06-07 15:50:59 EDT
This patch is going to have other side effects that aren't what is wanted (we
should only ever set request.device in autopart.py when going through and
verifying things).

Can you provide /tmp/anaconda.log and /tmp/syslog?
Comment 3 Chris Hollowell 2005-06-10 13:26:48 EDT
Attached is a patch which causes request.device to be set in the
kickstart.defineRaid() method if '--device' is specified.
Would setting request.device here be side-effect free?  I would
naively think so, since this is essentially what is done in 
definePartition() when '--onpart' is used.

I've tested the patch, and it also resolves this issue in our
Comment 4 Chris Hollowell 2005-06-10 13:28:18 EDT
Created attachment 115297 [details]
Another Patch Which Appears to Resolve This Issue
Comment 5 Chris Lumens 2007-03-14 16:16:52 EDT
Is this still a problem in RHEL5?

Note You need to log in before you can comment on or make changes to this bug.