RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 667089 - Anaconda-ks.cfg - Has wrong default entries for raid creation
Summary: Anaconda-ks.cfg - Has wrong default entries for raid creation
Keywords:
Status: CLOSED DUPLICATE of bug 591713
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.3
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-04 11:47 UTC by Francisco Lopez
Modified: 2011-01-04 15:15 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-04 15:15:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Francisco Lopez 2011-01-04 11:47:32 UTC
Description of problem:

anaconda-ks.cfg default entries for raid creation = raid.None

but should be like

part raid.11 --size=100 --grow --ondisk=sda --asprimary
part raid.12 --size=100 --grow --ondisk=sdb --asprimary
part raid.13 --size=100 --grow --ondisk=sdc --asprimary
part raid.14 --size=100 --grow --ondisk=sdd --asprimary
raid pv.10 --fstype "physical volume (LVM)" --level=RAID5 --spares=0 --device=md2 raid.11 raid.12 raid.13 raid.14


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

anaconda-13.21.82-1.el6.i686


How reproducible:

Always

Steps to Reproduce:

1.
2.
3.
  
Actual results:

#clearpart --linux --drives=sda,sdb,sdc,sdd,sde,sdf
{...}
#logvol swap --name=swaplv --vgname=rootvg --size=8192

#part raid.None --grow --asprimary --size=100
#part raid.None --grow --asprimary --size=100
#part raid.None --grow --asprimary --size=100
#part raid.None --grow --asprimary --size=100
#part /boot --fstype=ext4 --size=200
#part pv.cLJA05-EM12-EWj2-566x-D16L-nyya-VDPkp6 --grow --size=1

#part pv.0TOuXg-eYy7-FCEn-q9FC-rZu5-Ptml-0i0TYa --grow --size=1 

<<<EOF
Expected results:

part raid.11 --size=100 --grow --ondisk=sda --asprimary
part raid.12 --size=100 --grow --ondisk=sdb --asprimary
part raid.13 --size=100 --grow --ondisk=sdc --asprimary
part raid.14 --size=100 --grow --ondisk=sdd --asprimary
raid pv.10 --fstype "physical volume (LVM)" --level=RAID5 --spares=0 --device=md2 raid.11 raid.12 raid.13 raid.14



Additional info:

Comment 2 Chris Lumens 2011-01-04 15:15:09 UTC

*** This bug has been marked as a duplicate of bug 591713 ***


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