Skip to content

[release-4.17] OCPBUGS-64942: Expose prometheus tenancy label path as a proxy #15710

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
Open
wants to merge 1 commit into
base: release-4.17
Choose a base branch
from
Open

[release-4.17] OCPBUGS-64942: Expose prometheus tenancy label path as a proxy #15710

wants to merge 1 commit into from
+2 −0

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Nov 11, 2025

This is an automated cherry-pick of #15685

/assign PeterYurkovich

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Nov 11, 2025
Merged
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 11, 2025

@openshift-cherrypick-robot: Jira Issue OCPBUGS-64735 has been cloned as Jira Issue OCPBUGS-64942. Will retitle bug to link to clone.
/retitle [release-4.17] OCPBUGS-64942: Expose prometheus tenancy label path as a proxy

In response to this:

This is an automated cherry-pick of #15685

/assign PeterYurkovich

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.17] OCPBUGS-64735: Expose prometheus tenancy label path as a proxy [release-4.17] OCPBUGS-64942: Expose prometheus tenancy label path as a proxy Nov 11, 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 a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 11, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 11, 2025

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-64942, which is invalid:

  • expected dependent Jira Issue OCPBUGS-64735 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST 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.

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

In response to this:

This is an automated cherry-pick of #15685

/assign PeterYurkovich

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 requested review from florkbr and jhadvig November 11, 2025 14:33
@openshift-ci openshift-ci bot added the component/backend Related to backend label Nov 11, 2025
@PeterYurkovich PeterYurkovich mentioned this pull request Nov 11, 2025
Open
@PeterYurkovich
Copy link
Contributor

PeterYurkovich commented Nov 11, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 11, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 11, 2025

@PeterYurkovich: This pull request references Jira Issue OCPBUGS-64942, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.17.z) matches configured target version for branch (4.17.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-64735 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-64735 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
  • bug has dependents

Requesting review from QA contact:
/cc @etmurasaki

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.

@openshift-ci openshift-ci bot requested a review from etmurasaki November 11, 2025 15:33
@PeterYurkovich
Copy link
Contributor

PeterYurkovich commented Nov 11, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 11, 2025
@TheRealJon
Copy link
Member

TheRealJon commented Nov 11, 2025

/label backport-risk-assessed
/approve
/lgtm

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Nov 11, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 11, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, PeterYurkovich, TheRealJon

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 Nov 11, 2025
@PeterYurkovich
Copy link
Contributor

PeterYurkovich commented Nov 11, 2025

/retest

@etmurasaki
Copy link

etmurasaki commented Nov 11, 2025

/label qe-approved

@etmurasaki
Copy link

etmurasaki commented Nov 11, 2025

/verified by @etmurasaki

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Nov 11, 2025
@etmurasaki
Copy link

etmurasaki commented Nov 11, 2025

/retest

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 11, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 11, 2025

@etmurasaki: This PR has been marked as verified by @etmurasaki.

In response to this:

/verified by @etmurasaki

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
Copy link
Contributor

openshift-ci-robot commented Nov 12, 2025

/retest-required

Remaining retests: 0 against base HEAD 44c89c4 and 2 for PR HEAD 58a84ee in total

@jgbernalp
Copy link
Contributor

jgbernalp commented Nov 12, 2025

/test e2e-gcp-console

@PeterYurkovich
Copy link
Contributor

PeterYurkovich commented Nov 12, 2025

/retest

6 similar comments
@PeterYurkovich
Copy link
Contributor

PeterYurkovich commented Nov 12, 2025

/retest

@PeterYurkovich
Copy link
Contributor

PeterYurkovich commented Nov 12, 2025

/retest

@PeterYurkovich
Copy link
Contributor

PeterYurkovich commented Nov 13, 2025

/retest

@etmurasaki
Copy link

etmurasaki commented Nov 13, 2025

/retest

@PeterYurkovich
Copy link
Contributor

PeterYurkovich commented Nov 17, 2025

/retest

@PeterYurkovich
Copy link
Contributor

PeterYurkovich commented Nov 17, 2025

/retest

@jgbernalp
Copy link
Contributor

jgbernalp commented Nov 18, 2025

/test e2e-gcp-console

@PeterYurkovich
Copy link
Contributor

PeterYurkovich commented Nov 18, 2025

/retest

3 similar comments
@PeterYurkovich
Copy link
Contributor

PeterYurkovich commented Nov 18, 2025

/retest

@PeterYurkovich
Copy link
Contributor

PeterYurkovich commented Nov 18, 2025

/retest

@jgbernalp
Copy link
Contributor

jgbernalp commented Nov 19, 2025

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 19, 2025

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-console 58a84ee link true /test e2e-gcp-console

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@florkbr florkbr Awaiting requested review from florkbr

@jhadvig jhadvig Awaiting requested review from jhadvig

@etmurasaki etmurasaki Awaiting requested review from etmurasaki

Assignees

@yanpzhan yanpzhan

@sanketpathak sanketpathak

@yapei yapei

@TheRealJon TheRealJon

@PeterYurkovich PeterYurkovich

@XiyunZhao XiyunZhao

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. component/backend Related to backend jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a 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 Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

10 participants

@openshift-cherrypick-robot @openshift-ci-robot @PeterYurkovich @TheRealJon @etmurasaki @jgbernalp @yanpzhan @sanketpathak @yapei @XiyunZhao