DFBUGS-1509: [release-4.18] Use Required Pod anti affinity if Active MDS is not more than 1

[openshift-cherrypick-robot]

This is an automated cherry-pick of #3035

/assign malayparida2000

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references [Jira Issue DFBUGS-1509](https://issues.redhat.com//browse/DFBUGS-1509), which is invalid:

• expected the bug to target the "odf-4.18" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

This is an automated cherry-pick of #3035

/assign malayparida2000

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[malayparida2000]

/jira refresh

[openshift-ci-robot]

@malayparida2000: This pull request references [Jira Issue DFBUGS-1509](https://issues.redhat.com//browse/DFBUGS-1509), which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (odf-4.18) matches configured target version for branch (odf-4.18)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[malayparida2000]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: malayparida2000, openshift-cherrypick-robot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@openshift-cherrypick-robot: [Jira Issue DFBUGS-1509](https://issues.redhat.com//browse/DFBUGS-1509): All pull requests linked via external trackers have merged:

• red-hat-storage/ocs-operator#3036

[Jira Issue DFBUGS-1509](https://issues.redhat.com//browse/DFBUGS-1509) has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #3035

/assign malayparida2000

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[malayparida2000]

/cherry-pick release-4.17

[openshift-cherrypick-robot]

@malayparida2000: #3036 failed to apply on top of branch "release-4.17":

Applying: Use Required Pod anti affinity if Active MDS is not more than 1
Using index info to reconstruct a base tree...
M	controllers/defaults/placements.go
M	controllers/storagecluster/placement.go
M	controllers/storagecluster/placement_test.go
Falling back to patching base and 3-way merge...
Auto-merging controllers/storagecluster/placement_test.go
CONFLICT (content): Merge conflict in controllers/storagecluster/placement_test.go
Auto-merging controllers/storagecluster/placement.go
Auto-merging controllers/defaults/placements.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Use Required Pod anti affinity if Active MDS is not more than 1

In response to this:

/cherry-pick release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.