OCPBUGS-29728: cherry-pick:release-4.13: OCPBUGS-29244 Update VolumeSnapshot and VolumeSnapshotContent using JSON patch

[kaovilai]

Cherry-pick of commit ff71329 to branch release-4.13 to reduce flakes as seen in openshift/oadp-operator#1277
OCPBUGS-29244

[openshift-ci]

@kaovilai: all tests passed!

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[mpatlasov]

/retitle OCPBUGS-29728: cherry-pick:release-4.13: OCPBUGS-29244 Update VolumeSnapshot and VolumeSnapshotContent using JSON patch

[openshift-ci-robot]

@kaovilai: This pull request references Jira Issue OCPBUGS-29728, which is invalid:

• expected Jira Issue OCPBUGS-29728 to depend on a bug targeting a version in 4.14.0, 4.14.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Cherry-pick of commit ff71329 to branch release-4.13 to reduce flakes as seen in openshift/oadp-operator#1277
OCPBUGS-29244

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.

[mpatlasov]

/lgtm
/approve
/label backport-risk-assessed
/label cherry-pick-approved
/jira refresh

[openshift-ci-robot]

@mpatlasov: This pull request references Jira Issue OCPBUGS-29728, which is invalid:

• expected dependent Jira Issue OCPBUGS-29433 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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:

/lgtm
/approve
/label backport-risk-assessed
/label cherry-pick-approved
/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]

@mpatlasov: Can not set label cherry-pick-approved: Must be member in one of these teams: []

In response to this:

/lgtm
/approve
/label backport-risk-assessed
/label cherry-pick-approved
/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 kubernetes/test-infra repository.

[mpatlasov]

/assign @gnufied for approval

[openshift-ci]

@mpatlasov: GitHub didn't allow me to assign the following users: for, approval.

Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @gnufied for approval

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/test-infra repository.

[gnufied]

Usually it is not a good idea to patch things this way, but that is a discussion for another PR.

/approve

[gnufied]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gnufied, kaovilai, mpatlasov

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

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

[duanwei33]

QE is performing pre-merge verification with the open PR.

[duanwei33]

/label cherry-pick-approved

[duanwei33]

/label qe-approved

[openshift-ci-robot]

@kaovilai: This pull request references Jira Issue OCPBUGS-29728, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.13.z) matches configured target version for branch (4.13.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-29433 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-29433 targets the "4.14.0" version, which is one of the valid target versions: 4.14.0, 4.14.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

In response to this:

Cherry-pick of commit ff71329 to branch release-4.13 to reduce flakes as seen in openshift/oadp-operator#1277
OCPBUGS-29244

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.

[duanwei33]

/jira refresh

[openshift-ci-robot]

@duanwei33: This pull request references Jira Issue OCPBUGS-29728, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.13.z) matches configured target version for branch (4.13.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-29433 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-29433 targets the "4.14.0" version, which is one of the valid target versions: 4.14.0, 4.14.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), 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.

[openshift-ci-robot]

@kaovilai: Jira Issue OCPBUGS-29728: All pull requests linked via external trackers have merged:

• openshift/csi-external-snapshotter#141

Jira Issue OCPBUGS-29728 has been moved to the MODIFIED state.

In response to this:

Cherry-pick of commit ff71329 to branch release-4.13 to reduce flakes as seen in openshift/oadp-operator#1277
OCPBUGS-29244

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

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-csi-external-snapshotter-container-v4.13.0-202402221608.p0.gc8a7a09.assembly.stream.el8 for distgit ose-csi-external-snapshotter.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.13.0-0.nightly-2024-02-22-211710