The following was filed automatically by anaconda:
anaconda 220.127.116.11 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
File "/usr/bin/anaconda", line 1035, in <module>
KickstartValueError: The following problem occurred on line 15 of the kickstart file:
Tried to use undefined partition raid.None in RAID specification
Created attachment 413569 [details]
Attached traceback automatically from anaconda.
I used the partitioning as written out by anaconda on a installed system. It resulted in unreproducible installs
What happens if you change your kickstart file to use anything other than "None" for these names?
Let me try
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
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.
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.
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.
*** Bug 597347 has been marked as a duplicate of this bug. ***
*** Bug 628471 has been marked as a duplicate of this bug. ***
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.
*** Bug 667089 has been marked as a duplicate of this bug. ***
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
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.