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.
DescriptionHeinz Mauelshagen
2020-03-05 14:29:58 UTC
Description of problem:
The upstream resource-agents package contains a functionally limited 'Raid1' resource agent relative to supporting MD Clustered RAID1/10. This is the feature bz to track the development of a 'Raid1' cloned pacemaker resource agent with cluster enhancements. For instance, 'Raid1' has no notion of an MD array being clustered or not, thus can't reject creation of a respective resource properly or automatically adjust to it.
Version-Release number of selected component (if applicable):
All
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
See bz dependency for initial use/test case examples (subject to be copied and enhanced in this bz later)
Comment 1Heinz Mauelshagen
2020-03-11 12:02:01 UTC
We are developing the agent -> reassigned.
Comment 2Heinz Mauelshagen
2020-03-13 16:31:32 UTC
Including test cases from closed 1810561 here.
Test cases:
- active-passive
- create MD resources for all levels (0/1/4/5/6/10) with force_clones=false
- check they get started properly
- put (single host) filesystems (xfs, ext4, gfs2) on top and load with I/O
- define ordering constraints for ^
- move them to other node manually
- disable/enable them
- add/remove legs to/from raid1
- fail/fence a node and check if they get started correctly
on another online node
- fail access to MD array leg(s) on its active node
and analyse MD/resource/filesystem behaviour
- reboot whole cluster and check for resource properly started
- update the resource option force_clones to true
- clone the resource (should fail on single host MD arrays but it doesn't)
- test for data corruption (even with gfs2 on top)
- remove all resources in/out of order and check for proper removal
- active-active
- create clustered MD resources for levels 1 and 10
- check they get started properly
- clone them
- check they get started properly on all other online nodes
- add/remove legs to/from RAID1
- try reshaping RAID10
- disable/enable them
- fail a node and check if they get started correctly on another node
- fail access to MD array leg(s) on any/multiple nodes
and analyse MD/resource/filesystem behaviour
- remove all resources in/out of order and check for proper removal
Comment 3Heinz Mauelshagen
2020-04-08 12:09:24 UTC
Resource agent in final internal pre-upstream review by Oyvind Albrigtsen et. al. on the cluster team.
Delaying switiching bz status to POST until the pull upstream requests..
Comment 5Oyvind Albrigtsen
2020-04-15 14:44:14 UTC
Comment 7Oyvind Albrigtsen
2020-04-22 12:46:58 UTC
Agent merged upstream.
Comment 15Heinz Mauelshagen
2020-10-26 16:20:28 UTC
As we support clustered MD RAID1 and RAID10 in RHEL8, the mdraid resource agent is mandatory for managing such arrays.
Comment 49RHEL Program Management
2023-09-22 18:35:48 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 50RHEL Program Management
2023-09-22 18:37:19 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.