Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DFBUGS-1421: [release-4.17] remove hard-coded namespace from noobaa #226

Open
wants to merge 1 commit into
base: release-4.17
Choose a base branch
from

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #218

/assign agarwal-mudit

this commit removes the hard-coded namespace
for noobaa collection to collect all the
resources in correct namespace

Signed-off-by: yati1998 <[email protected]>
Copy link
Contributor

openshift-ci bot commented Feb 4, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign obnoxxx for approval. For more information see the Code Review Process.

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

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

@agarwal-mudit agarwal-mudit changed the title [release-4.17] remove hard-coded namespace from noobaa DFBUGS-1421: [release-4.17] remove hard-coded namespace from noobaa Feb 4, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid jira ticket of any type label Feb 4, 2025
@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Feb 4, 2025

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

  • expected the bug to target either version "odf-4.17.3." or "openshift-odf-4.17.3.", but it targets "odf-4.17.4" 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 an automated cherry-pick of #218

/assign agarwal-mudit

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/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting label Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting jira/valid-reference Indicates that this PR references a valid jira ticket of any type
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants