Red Hat Bugzilla – Bug 159193
When creating LVM on RAID partitions the anaconda-ks.cfg is invalid
Last modified: 2008-06-21 16:07:23 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040808 Firefox/0.9.3
Description of problem:
Description of problem: When creating LVM on RAID partitions the
anaconda-ks.cfg is invalid. In particular, the "raid pv.20 --fstype
physical volume (LVM) --level=RAID1 raid.17 raid.18" line that was
created should have had the fstype quoted since it contains embedded
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Do an install of el4 with lvm on raid.
2. reinstall using the partition information from anaconda-ks.cfg
3. Install fails with "Tried to use an undefined partition in RAID specification"
Actual Results: Backtrace occurred.
Expected Results: Normal install
The following line was generated by anaconda:
raid pv.26 --fstype physical volume (LVM) --level=RAID1 raid.24 raid.25
The above is the problem. Removing the --fstype part fixes the problem.
I suppose putting quotes around "physical volume (LVM)" would also fix it but I have not tested this.
This is the same bug as 119243 which was supposed to be fixed in el3-u3.
Fixed in CVS on all branches.