Bug 591713

Summary: KickstartValueError: The following problem occurred on line 15 of the kickstart file: Tried to use undefined partition raid.None in RAID specificationusUsing
Product: Red Hat Enterprise Linux 6 Reporter: Dennis Gilmore <dgilmore>
Component: anacondaAssignee: Chris Lumens <clumens>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: atodorov, flopezyg, jmoyer, jstodola
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: anaconda_trace_hash:23e61d66771883eb10b4d1d4d444486d6980cea176acae868cd7b7d6878d841a
Fixed In Version: anaconda-13.21.85-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 12:29:27 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:
Bug Depends On:    
Bug Blocks: 647893    
Attachments:
Description Flags
Attached traceback automatically from anaconda. none

Description Dennis Gilmore 2010-05-12 21:22:34 UTC
The following was filed automatically by anaconda:
anaconda 13.21.20.5 exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/kickstart.py", line 826, in execute
    raise KickstartValueError, formatErrorMsg(self.lineno, msg="Tried to use undefined partition %s in RAID specification" % member)
  File "/usr/lib/anaconda/kickstart.py", line 1086, in execute
    obj.execute(self.anaconda)
  File "/usr/bin/anaconda", line 1035, in <module>
    ksdata.execute()
KickstartValueError: The following problem occurred on line 15 of the kickstart file:

Tried to use undefined partition raid.None in RAID specification

Comment 1 Dennis Gilmore 2010-05-12 21:22:36 UTC
Created attachment 413569 [details]
Attached traceback automatically from anaconda.

Comment 2 Dennis Gilmore 2010-05-12 21:24:33 UTC
I used the partitioning as written out by anaconda on a installed system. It resulted in unreproducible installs

Comment 3 Chris Lumens 2010-05-12 21:25:44 UTC
What happens if you change your kickstart file to use anything other than "None" for these names?

Comment 4 Dennis Gilmore 2010-05-12 21:27:21 UTC
Let me try

Comment 6 RHEL Program Management 2010-05-12 23:18:54 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 7 Chris Lumens 2010-06-04 17:50:14 UTC
The anaconda-ks.cfg is provided as a basis for getting started with kickstart.  The partitioning section in particular is commented out as it's up to you to verify it's correct.  We've left it this way for as long as I can remember.

The fact that you've got "None" in there means we are not being provided with a UUID for those RAID volumes.  If you can reproduce this with something other than "None" in those specifiers, it'd be a much more high priority problem.

Comment 8 RHEL Program Management 2010-06-04 17:55:22 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

Comment 9 Dennis Gilmore 2010-06-08 17:07:58 UTC
It works with Values specified there.  and it works with the partitioning as written out by anaconda in RHEL-5,  this is a regression from RHEL-5's anaconda and at the very least needs documenting because i was unable to find any anywhere.

Comment 10 David Cantrell 2010-06-16 18:54:00 UTC
*** Bug 597347 has been marked as a duplicate of this bug. ***

Comment 11 Chris Lumens 2010-08-30 13:02:51 UTC
*** Bug 628471 has been marked as a duplicate of this bug. ***

Comment 13 Chris Lumens 2010-12-16 15:41:00 UTC
This should be fixed in the next build of anaconda.  I tested with LVM built on top of a combination of RAID and regular partitions, and the IDs matched up correctly.

Comment 15 Chris Lumens 2011-01-04 15:15:09 UTC
*** Bug 667089 has been marked as a duplicate of this bug. ***

Comment 17 Alexander Todorov 2011-04-05 11:22:51 UTC
Tested with anaconda-13.21.109. The anaconda-ks.cfg file doesn't contain raid.None entries, instead there is: 

part raid.253002 --size=9000

Comment 18 errata-xmlrpc 2011-05-19 12:29:27 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0530.html