Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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.
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.