Skip to content

DFBUGS-1790:[release-4.18] controllers: update csi-op subscription based on provider version#316

Merged
openshift-merge-bot[bot] merged 1 commit intored-hat-storage:release-4.18from
openshift-cherrypick-robot:cherry-pick-315-to-release-4.18
Mar 7, 2025
Merged

DFBUGS-1790:[release-4.18] controllers: update csi-op subscription based on provider version#316
openshift-merge-bot[bot] merged 1 commit intored-hat-storage:release-4.18from
openshift-cherrypick-robot:cherry-pick-315-to-release-4.18

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #315

/assign leelavg

along with other depedent operators of client-op we also need to update
csi-op after client-op gets upgraded

Signed-off-by: Leela Venkaiah G <[email protected]>
@leelavg leelavg changed the title [release-4.18] controllers: update csi-op subscription based on provider version DFBUGS-1790:[release-4.18] controllers: update csi-op subscription based on provider version Mar 7, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid jira ticket of any type jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels Mar 7, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 7, 2025

@openshift-cherrypick-robot: This pull request references [Jira Issue DFBUGS-1790](https://issues.redhat.com//browse/DFBUGS-1790), 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.

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

Details

In response to this:

This is an automated cherry-pick of #315

/assign leelavg

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
Copy link
Copy Markdown
Member

Madhu-1 commented Mar 7, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting and removed jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels Mar 7, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 7, 2025

@Madhu-1: This pull request references [Jira Issue DFBUGS-1790](https://issues.redhat.com//browse/DFBUGS-1790), 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.

Details

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.

@Madhu-1
Copy link
Copy Markdown
Member

Madhu-1 commented Mar 7, 2025

/lgtm
/approve

@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Mar 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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-ci openshift-ci bot added the approved label Mar 7, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 330f685 into red-hat-storage:release-4.18 Mar 7, 2025
11 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 7, 2025

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

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

Details

In response to this:

This is an automated cherry-pick of #315

/assign leelavg

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-important Referenced Jira bug's severity is important 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 size/S

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants