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 1810561 - Test new pacemaker MD Clustered RAID resource agent once available
Summary: Test new pacemaker MD Clustered RAID resource agent once available
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: resource-agents
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.3
Assignee: Oyvind Albrigtsen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1797674
Blocks: 1810577 2166683
TreeView+ depends on / blocked
 
Reported: 2020-03-05 13:58 UTC by Heinz Mauelshagen
Modified: 2023-02-02 16:08 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-13 16:32:16 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3977931 0 None None None 2020-11-17 19:19:42 UTC

Description Heinz Mauelshagen 2020-03-05 13:58:02 UTC
Description of problem:
Keep track of testing once dependent bug's posted for Radi1 agent inclusion.

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

How reproducible:
Not yetm waiting for Raid1 agent inclusion.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
The Raid1 resource agent is suitable to manage single-node MD RAID
arrays of any layout active-passive and clustered MD RAID1/10 active-active.

It has been developed without clustering in mind but supports a 'force_clones' configuration option to allow for creating clustered RAID arrays in a limited way when set to 'true'.  We are aiming to clone this resource agent and enhance it relative to its cluster functionality.

This very bz defines test coverage once the exisiting Raid1 agent is packaged.

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


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