Skip to content

Conversation

@leelavg
Copy link
Contributor

@leelavg leelavg commented May 21, 2025

manual cherry-pick of #365

leelavg added 2 commits May 21, 2025 07:41
in remote client clusters noobaa should follow client-operator
subscription channel. we had tied noobaa feature usage with operator
upgrade resulting in operator not upgrading from 4.17.

Signed-off-by: Leela Venkaiah G <[email protected]>
Signed-off-by: Leela Venkaiah G <[email protected]>
@openshift-ci
Copy link

openshift-ci bot commented May 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: leelavg

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

@leelavg
Copy link
Contributor Author

leelavg commented May 21, 2025

/jira cherrypick DFBUGS-1872

@openshift-ci-robot
Copy link

openshift-ci-robot commented May 21, 2025

@leelavg: [Jira Issue DFBUGS-1872](https://issues.redhat.com//browse/DFBUGS-1872) has been cloned as [Jira Issue DFBUGS-2587](https://issues.redhat.com//browse/DFBUGS-2587). Will retitle bug to link to clone.
/retitle DFBUGS-2587: [release-4.18] upgrade noobaa along with client-operator

Details

In response to this:

/jira cherrypick DFBUGS-1872

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 openshift-ci bot changed the title [release-4.18] upgrade noobaa along with client-operator DFBUGS-2587: [release-4.18] upgrade noobaa along with client-operator May 21, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate 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 May 21, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 21, 2025

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

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

Details

In response to this:

manual cherry-pick of #365

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-merge-robot
Copy link

PR needs rebase.

Details

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-sigs/prow repository.

@leelavg
Copy link
Contributor Author

leelavg commented May 28, 2025

there will be a new PR for removing Noobaa from client deployments.

@leelavg leelavg closed this May 28, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 28, 2025

@leelavg: This pull request references [Jira Issue DFBUGS-2587](https://issues.redhat.com//browse/DFBUGS-2587). The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

manual cherry-pick of #365

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/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid jira ticket of any type needs-rebase size/M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants