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 2083426 - storage role raid_level "striped" is not supported
Summary: storage role raid_level "striped" is not supported
Alias: None
Deadline: 2022-06-20
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rhel-system-roles
Version: 8.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.7
Assignee: Rich Megginson
QA Contact: David Jež
Michal Stubna
Whiteboard: role:storage
Depends On: 2083410
Blocks: 2098226
TreeView+ depends on / blocked
Reported: 2022-05-10 01:25 UTC by Rich Megginson
Modified: 2022-11-08 15:12 UTC (History)
9 users (show)

Fixed In Version: rhel-system-roles-1.19.1-1.el8
Doc Type: Bug Fix
Doc Text:
.The `storage` RHEL System Role now correctly supports `striped` and `raid0` levels for LVM volumes The `storage` RHEL System Role previously incorrectly reported RAID levels `striped` and `raid0` as not supported for LVM volumes. This is now fixed and the role can now correctly create LVM volumes of all RAID levels supported by LVM: `raid0`, `raid1`, `raid4`, `raid5`, `raid6`, `raid10`, `striped` and `mirror`.
Clone Of: 2083410
: 2098226 (view as bug list)
Last Closed: 2022-11-08 09:41:24 UTC
Type: Bug
Target Upstream Version:
pkettman: needinfo+

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github linux-system-roles storage pull 272 0 None Merged LVM RAID raid0 level support 2022-06-02 23:29:32 UTC
Red Hat Issue Tracker RHELPLAN-121502 0 None None None 2022-11-08 15:12:56 UTC
Red Hat Product Errata RHEA-2022:7568 0 None None None 2022-11-08 09:41:55 UTC

Description Rich Megginson 2022-05-10 01:25:54 UTC
+++ This bug was initially created as a clone of Bug #2083410 +++

Description of problem:

The documentation for the storage role lists "striped" as a valid value for the "raid_level" option, but trying to use it gives an error:

blivet.errors.DeviceError: RAID level striped is an invalid value. Must be one of (raid10, raid1, raid4, linear, raid5, raid6, raid0)

We should either remove "striped" from the docs, or make "striped" an alias for "raid0" (if they are indeed the same thing).

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 17 errata-xmlrpc 2022-11-08 09:41:24 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (rhel-system-roles bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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