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

OCPBUGS-42371: Update core reference to ignore automatically-added operator labels #40

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

lack
Copy link
Member

@lack lack commented Sep 26, 2024

Signed-off-by: Jim Ramsay [email protected]

Copy link

openshift-ci bot commented Sep 26, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lack
Once this PR has been reviewed and has the lgtm label, please assign marsik for approval. For more information see the Kubernetes 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

@openshift-ci-robot
Copy link
Collaborator

@lack: This pull request references Jira Issue OCPBUGS-42371, 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 (4.18.0) matches configured target version for branch (4.18.0)
  • 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.

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

In response to this:

Signed-off-by: Jim Ramsay [email protected]

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.

@lack
Copy link
Member Author

lack commented Oct 7, 2024

/cc @imiller0

@openshift-ci openshift-ci bot requested a review from imiller0 October 7, 2024 14:39
@@ -4,3 +4,6 @@ metadata:
name: openshift-nmstate
annotations:
workload.openshift.io/allowed: management
labels:
name: openshift-nmstate
openshift.io/cluster-monitoring: "true"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The name appears to be automatically added (though I'm not sure why...) . The monitoring looks to be a specific opt-in. If that is the case it should either be included in the reference CR as well or ignored via metadata.yaml if we don't care.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MarSik : What's your verdict? I don't know enough about either of these, or the core RDS, to know which, if either, should be optional.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need someone from nmstate or networking here, I have no idea.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 8, 2024
@lack lack force-pushed the reference/permissive_labels branch from d54c223 to 2f92d0c Compare October 9, 2024 02:05
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants