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.

Sign up for GitHub

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

Jump to bottom

add pf-status-relay-operator to dependents #5994

Open
wants to merge 1 commit into
base: openshift-4.19
Choose a base branch
from
Open

add pf-status-relay-operator to dependents #5994

wants to merge 1 commit into from

Conversation

ashwindasr
Copy link
Contributor

@ashwindasr ashwindasr commented Jan 15, 2025 •
edited
Loading

Follows upstream change: openshift/pf-status-relay-operator#34

Fixes error seen in https://art-jenkins.apps.prod-stable-spoke1-dc-iad2.itup.redhat.com/job/aos-cd-builds/job/build%252Focp4/13833/

 ERROR Related image contains kube-rbac-proxy but this does not have pf-status-relay-operator in dependents

@ashwindasr
Copy link
Contributor Author

/cherry-pick openshift-4.18

@openshift-cherrypick-robot
Copy link

@ashwindasr: once the present PR merges, I will cherry-pick it on top of openshift-4.18 in a new PR and assign it to you.

In response to this:

/cherry-pick openshift-4.18

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.

@ashwindasr
Copy link
Contributor Author

ashwindasr commented Jan 15, 2025 •
edited
Loading

/hold

Until upstream PR has merged

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 15, 2025
rayfordj
rayfordj approved these changes Jan 15, 2025
View reviewed changes
Copy link
Contributor

@rayfordj rayfordj left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 15, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 15, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rayfordj

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

The pull request process is described 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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 15, 2025
@ashwindasr ashwindasr added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rayfordj rayfordj rayfordj approved these changes

Assignees

@rayfordj rayfordj

Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@ashwindasr @openshift-cherrypick-robot @rayfordj