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.
DescriptionJonathan Earl Brassow
2019-08-15 17:15:20 UTC
This is the tracker bug for all the bugs / steps for enabling cluster RAID1 support in LVM. Each bug being tracked must be:
1) Be detailed enough to make implementation a straightforward engineering exercise. (i.e. set clear boundaries on what is expected of the implementation)
2) Lay out clearly for QA the level of testing required
3) Lay out clearly for docs what is required for documentation
Comment 1Jonathan Earl Brassow
2019-08-15 17:18:42 UTC
(In reply to Jonathan Earl Brassow from comment #0)
> This is the tracker bug for all the bugs / steps for enabling cluster RAID1
> support in LVM. Each bug being tracked must be:
> 1) Be detailed enough to make implementation a straightforward engineering
> exercise. (i.e. set clear boundaries on what is expected of the
> implementation)
> 2) Lay out clearly for QA the level of testing required
> 3) Lay out clearly for docs what is required for documentation
Tracking:
[1?][2?][3?] Bug 873305 - LVM support for MD cluster RAID1
Comment 2Jonathan Earl Brassow
2019-08-15 17:27:06 UTC
(In reply to Jonathan Earl Brassow from comment #0)
> This is the tracker bug for all the bugs / steps for enabling cluster RAID1
> support in LVM. Each bug being tracked must be:
> 1) Be detailed enough to make implementation a straightforward engineering
> exercise. (i.e. set clear boundaries on what is expected of the
> implementation)
> 2) Lay out clearly for QA the level of testing required
> 3) Lay out clearly for docs what is required for documentation
Tracking:
[1-][2-][3-] Bug 1741644 - [RFE] Support for cluster RAID1
[1?][2?][3?] Bug 873305 - LVM support for MD cluster RAID1
Comment 3Heinz Mauelshagen
2019-08-16 11:56:49 UTC
MD kernel supports cluster RAID1 and RAID10, thus changed the summary to reflect the fact that both features are aimed at and tracked in this bz. Depending on design and technical implementation retrenchments, we'll have to decide if both can ideally be supported in one release or have to be scheduled differently.
Comment 8RHEL Program Management
2022-04-28 07:29:33 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.