Skip to content

DFBUGS-4007: [release-4.22] updating the note for drpolicy creation for third party storage#2809

Merged
openshift-merge-bot[bot] merged 1 commit into
red-hat-storage:release-4.22from
openshift-cherrypick-robot:cherry-pick-2805-to-release-4.22
May 19, 2026
Merged

DFBUGS-4007: [release-4.22] updating the note for drpolicy creation for third party storage#2809
openshift-merge-bot[bot] merged 1 commit into
red-hat-storage:release-4.22from
openshift-cherrypick-robot:cherry-pick-2805-to-release-4.22

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #2805

/assign SanjalKatiyar

@vbnrh
Copy link
Copy Markdown
Member

vbnrh commented May 19, 2026

/retitle DFBUGS-4007: [release-4.22] updating the note for drpolicy creation for third party storage

@openshift-ci openshift-ci Bot changed the title [release-4.22] updating the note for drpolicy creation for third party storage DFBUGS-4007: [release-4.22] updating the note for drpolicy creation for third party storage May 19, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid jira ticket of any type labels May 19, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 19, 2026

@openshift-cherrypick-robot: This pull request references [Jira Issue DFBUGS-4007](https://redhat.atlassian.net/browse/DFBUGS-4007), which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.22) matches configured target version for branch (odf-4.22)
  • 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 (ammahapa@redhat.com), skipping review request.

Details

In response to this:

This is an automated cherry-pick of #2805

/assign SanjalKatiyar

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 openshift-ci-robot added the jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting label May 19, 2026
@SanjalKatiyar
Copy link
Copy Markdown
Collaborator

/approve
/lgtm

@openshift-ci openshift-ci Bot added the lgtm label May 19, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 19, 2026

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-merge-bot openshift-merge-bot Bot merged commit 2e84f95 into red-hat-storage:release-4.22 May 19, 2026
5 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 19, 2026

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

[Jira Issue DFBUGS-4007](https://redhat.atlassian.net/browse/DFBUGS-4007) has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #2805

/assign SanjalKatiyar

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting jira/valid-reference Indicates that this PR references a valid jira ticket of any type lgtm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants