DFBUGS-979: Revert "csi: disable fencing in Rook"

[subhamkrai]

This reverts commit 4e761bd.

Checklist:

• Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
• Reviewed the developer guide on Submitting a Pull Request
• Pending release notes updated with breaking and/or notable changes for the next minor release.
• Documentation has been updated, if necessary.
• Unit tests have been added, if necessary.
• Integration tests have been added, if necessary.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: subhamkrai

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 [subhamkrai]

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

[subhamkrai]

@sp98 PTAL we need to revert the fix and move to next patch release as previous patch release was cve only

[sp98]

@sp98 PTAL we need to revert the fix and move to next patch release as previous patch release was cve only

@subhamkrai Why are you enabling it again? Please add more details about this. Also, the CI is failing.

[subhamkrai]

@sp98 PTAL we need to revert the fix and move to next patch release as previous patch release was cve only

@subhamkrai Why are you enabling it again? Please add more details about this. Also, the CI is failing.

CI failure is kind of not related, CI is failing at the cluster creation stage which is due to the old version.

We are reverting the changes as it merged in CVE only patch

[agarwal-mudit]

@subhamkrai is there a bug for this? please do add

[subhamkrai]

@subhamkrai is there a bug for this? please do add

@agarwal-mudit bug is to disable the networkFence but since the changes were merged in CVE only patch we need to revert the change for now and fix in right version. So, technically no bug for this PR as it is reverting the changes only

[agarwal-mudit]

We need a bug for every change in z-stream (unless its test only change), please create one and reach out to Sunil/Karthick for approvals

[subhamkrai]

We need a bug for every change in z-stream (unless its test only change), please create one and reach out to Sunil/Karthick for approvals

okay 👍🏽

[openshift-ci-robot]

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

• expected the bug to target the "odf-4.15.9" 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 reverts commit 4e761bd.

Checklist:

• Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
• Reviewed the developer guide on Submitting a Pull Request
• Pending release notes updated with breaking and/or notable changes for the next minor release.
• Documentation has been updated, if necessary.
• Unit tests have been added, if necessary.
• Integration tests have been added, if necessary.

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.

[subhamkrai]

/jira refresh

[openshift-ci-robot]

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

• expected the bug to target the "odf-4.15.9" 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:

/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.

[openshift-ci-robot]

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

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead

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 reverts commit 4e761bd.

Checklist:

• Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
• Reviewed the developer guide on Submitting a Pull Request
• Pending release notes updated with breaking and/or notable changes for the next minor release.
• Documentation has been updated, if necessary.
• Unit tests have been added, if necessary.
• Integration tests have been added, if necessary.

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.

[sp98]

/jira refresh

[openshift-ci-robot]

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

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead

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:

/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.

[sunilheggodu]

/jira refresh

[openshift-ci-robot]

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

3 validation(s) were run on this bug

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

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.

[openshift-ci-robot]

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

• red-hat-storage/rook#797

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

In response to this:

This reverts commit 4e761bd.

Checklist:

• Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
• Reviewed the developer guide on Submitting a Pull Request
• Pending release notes updated with breaking and/or notable changes for the next minor release.
• Documentation has been updated, if necessary.
• Unit tests have been added, if necessary.
• Integration tests have been added, if necessary.

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.