Bug 670643 - Missing --label= flag for raid kickstart option
Summary: Missing --label= flag for raid kickstart option
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Chris Lumens
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-18 21:40 UTC by Jeff Vier
Modified: 2018-11-28 21:02 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-20 15:11:43 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jeff Vier 2011-01-18 21:40:23 UTC
Description of problem:
"partition" option has a --label= flag.  "raid" option should, too.

Version-Release number of selected component (if applicable):
6.0, 5.6, 5.5, ...

How reproducible:
Always

Steps to Reproduce:
1. In kickstart config:
...
part raid.0 --ondisk=sda --asprimary --fstype ext2 --size=100
part raid.1 --ondisk=sdb --asprimary --fstype ext2 --size=100
raid /boot --label=boot --level=1 --device=md0 --fstype=ext2 raid.0 raid.1
...

2. initiate kickstart of the node

3. observe console
  
Actual results:
Error halting kickstart

Expected results:
/dev/md0 gets labeled, goes into /etc/fstab referenced as such.

Additional info:
Work-around is running `e2label /dev/md0 /boot` in %post and then hacking the /etc/fstab, but that's non-ideal.

Comment 2 Chris Lumens 2011-01-20 15:11:43 UTC
Yeah, that's kind of a glaring omission isn't it?

I've committed this to master for both anaconda and pykickstart, which means it'll be in F15 and (eventually) RHEL7.  If you can't wait that long - and I understand that could be a while - please raise this issue through your support person who will make sure it gets on our schedule, etc.  Thanks.

Comment 3 Jeff Vier 2011-01-20 18:12:27 UTC
Do you mind linking to the precise commit?  I'm curious....


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