DFBUGS-1028: csi-snapshotter flag typo; upgrade csi-snapshotter

[Madhu-1]

This is backport of rook#15196 to 4.18

Signed-off-by: Steven Kreitzer [email protected]
(cherry picked from commit 463d9fb)

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-robot]

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

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA 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 is backport of rook#15196 to 4.18

Signed-off-by: Steven Kreitzer [email protected]
(cherry picked from commit 463d9fb)

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.

[Madhu-1]

/jira refresh

[openshift-ci-robot]

@Madhu-1: This pull request references [Jira Issue DFBUGS-1028](https://issues.redhat.com//browse/DFBUGS-1028), which is valid. The bug has been moved to the POST state.

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 ASSIGNED, 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.

[subhamkrai]

lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: Madhu-1, 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

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]

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

• red-hat-storage/rook#799

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

In response to this:

This is backport of rook#15196 to 4.18

Signed-off-by: Steven Kreitzer [email protected]
(cherry picked from commit 463d9fb)

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.