OCPBUGS-62765: port metric acm_managed_cluster_worker_cores:max to OCP 4.16 #2719

elgnay · 2025-10-20T10:00:46Z

I added CHANGELOG entry for this change.
No user facing changes, so no entry in CHANGELOG was needed.

openshift-ci-robot · 2025-10-20T10:04:19Z

@elgnay: This pull request references Jira Issue OCPBUGS-62765, which is invalid:

expected the bug to target the "4.16.z" version, but no target version was set
release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-62765 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

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.

elgnay · 2025-10-20T10:06:39Z

/jira refresh

openshift-ci-robot · 2025-10-20T10:06:43Z

@elgnay: This pull request references Jira Issue OCPBUGS-62765, which is invalid:

expected the bug to target the "4.16.z" version, but no target version was set
release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-62765 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

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.

Signed-off-by: Yang Le <[email protected]>

elgnay · 2025-10-20T10:26:55Z

/jira refresh

openshift-ci-robot · 2025-10-20T10:26:59Z

@elgnay: This pull request references Jira Issue OCPBUGS-62765, which is invalid:

expected the bug to target the "4.16.z" version, but no target version was set
release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-62765 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

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.

elgnay · 2025-10-21T00:51:32Z

/retest

elgnay · 2025-10-21T04:27:53Z

/test e2e-agnostic-operator

elgnay · 2025-10-21T10:55:00Z

/test e2e-agnostic-operator

elgnay · 2025-10-22T00:59:30Z

/test e2e-agnostic-operator

juzhao · 2025-10-24T07:50:41Z

/jira refresh

openshift-ci-robot · 2025-10-24T07:50:44Z

@juzhao: This pull request references Jira Issue OCPBUGS-62765, which is invalid:

expected the bug to target the "4.16.z" version, but no target version was set
expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead
release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected Jira Issue OCPBUGS-62765 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

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.

juzhao · 2025-10-24T07:56:32Z

/jira refresh

openshift-ci-robot · 2025-10-24T07:56:37Z

@juzhao: This pull request references Jira Issue OCPBUGS-62765, which is invalid:

expected Jira Issue OCPBUGS-62765 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

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.

juzhao · 2025-10-24T07:59:02Z

/jira refresh

openshift-ci-robot · 2025-10-24T07:59:10Z

@juzhao: This pull request references Jira Issue OCPBUGS-62765, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.16.z) matches configured target version for branch (4.16.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-48069 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-48069 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
bug has dependents

Requesting review from QA contact:
/cc @juzhao

In response to this:

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.

juzhao · 2025-10-24T08:02:49Z

/retest-required

simonpasquier · 2025-10-27T14:27:00Z

/hold

there's no need to update the telemetry allow-list in release branches. The reference is always the main/master branch of CMO.

simonpasquier · 2025-10-27T14:59:21Z

/hold cancel

sorry I'm just back from PTO and I misunderstood the purpose of the PR. Can you update the PR to only add the acm_managed_cluster_worker_cores:max metric and remove the owners change for acm_managed_cluster_info since it's unrelated?

openshift-ci-robot · 2025-10-27T15:05:05Z

@simonpasquier: This pull request references Jira Issue OCPBUGS-62765, which is invalid:

expected Jira Issue OCPBUGS-62765 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

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.

simonpasquier · 2025-10-27T15:12:41Z

@elgnay please also note that we have an issue with the CI for the release-4.16 branch. We're in the process of fixing it but there's no need to /retest the failing job for now :)

simonpasquier · 2025-10-27T16:28:12Z

/hold

until #2727 merges

elgnay · 2025-10-28T07:31:12Z

Thanks, @simonpasquier. I’ve double-checked and confirmed that the metric has been included since OCP 4.17. Do I still need to create bugs for OCP 4.17 and later?

simonpasquier · 2025-10-28T09:08:58Z

yes for traceability.

/hold cancel

simonpasquier · 2025-10-28T09:09:07Z

/test e2e-agnostic-operator

simonpasquier · 2025-10-28T09:10:35Z

/jira refresh

openshift-ci-robot · 2025-10-28T09:10:40Z

@simonpasquier: This pull request references Jira Issue OCPBUGS-62765, which is invalid:

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

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.

simonpasquier · 2025-10-28T09:11:41Z

/jira refresh

openshift-ci-robot · 2025-10-28T09:11:47Z

@simonpasquier: This pull request references Jira Issue OCPBUGS-62765, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.16.z) matches configured target version for branch (4.16.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-63620 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-63620 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
bug has dependents

Requesting review from QA contact:
/cc @juzhao

In response to this:

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.

simonpasquier · 2025-10-28T09:12:25Z

/approve
/label backport-risk-assessed

simonpasquier · 2025-10-28T09:12:45Z

/lgtm

simonpasquier · 2025-10-28T09:13:01Z

/verified by existing tests

openshift-ci-robot · 2025-10-28T09:13:12Z

@simonpasquier: This PR has been marked as verified by existing tests.

In response to this:

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 · 2025-10-28T09:14:05Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elgnay, simonpasquier

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:

~~OWNERS~~ [simonpasquier]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci · 2025-10-28T09:14:08Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elgnay, simonpasquier

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:

~~OWNERS~~ [simonpasquier]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci · 2025-10-28T15:27:40Z

@elgnay: all tests passed!

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.

openshift-ci-robot · 2025-10-28T15:30:42Z

@elgnay: Jira Issue OCPBUGS-62765: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

openshift/telemeter#566 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-62765 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

In response to this:

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 bot requested review from marioferh and rexagod October 20, 2025 10:01

elgnay changed the title ~~port metric acm_managed_cluster_worker_cores:max to OCP 4.16~~ OCPBUGS-62765: port metric acm_managed_cluster_worker_cores:max to OCP 4.16 Oct 20, 2025

OCPBUGS-62765: port ACM metrics to OCP 4.16

daef816

Signed-off-by: Yang Le <[email protected]>

elgnay force-pushed the port-acm-metrics branch from 98061a9 to daef816 Compare October 20, 2025 10:26

openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Oct 24, 2025

openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 24, 2025

openshift-ci bot requested a review from juzhao October 24, 2025 07:59

openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 27, 2025

openshift-ci-robot added jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. and removed jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Oct 27, 2025

openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 27, 2025

openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 28, 2025

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 Oct 28, 2025

openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 28, 2025

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 28, 2025

openshift-ci bot assigned simonpasquier Oct 28, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 28, 2025

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 28, 2025

openshift-merge-bot bot merged commit 738eb25 into openshift:release-4.16 Oct 28, 2025
17 checks passed

OCPBUGS-62765: port metric acm_managed_cluster_worker_cores:max to OCP 4.16 #2719

OCPBUGS-62765: port metric acm_managed_cluster_worker_cores:max to OCP 4.16 #2719

Uh oh!

Conversation

elgnay commented Oct 20, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Oct 20, 2025

Uh oh!

elgnay commented Oct 20, 2025

Uh oh!

openshift-ci-robot commented Oct 20, 2025

Uh oh!

elgnay commented Oct 20, 2025

Uh oh!

openshift-ci-robot commented Oct 20, 2025

Uh oh!

elgnay commented Oct 21, 2025

Uh oh!

elgnay commented Oct 21, 2025

Uh oh!

elgnay commented Oct 21, 2025

Uh oh!

elgnay commented Oct 22, 2025

Uh oh!

juzhao commented Oct 24, 2025

Uh oh!

openshift-ci-robot commented Oct 24, 2025

Uh oh!

juzhao commented Oct 24, 2025

Uh oh!

openshift-ci-robot commented Oct 24, 2025

Uh oh!

juzhao commented Oct 24, 2025

Uh oh!

openshift-ci-robot commented Oct 24, 2025

Uh oh!

juzhao commented Oct 24, 2025

Uh oh!

simonpasquier commented Oct 27, 2025

Uh oh!

simonpasquier commented Oct 27, 2025

Uh oh!

openshift-ci-robot commented Oct 27, 2025

Uh oh!

simonpasquier commented Oct 27, 2025

Uh oh!

simonpasquier commented Oct 27, 2025

Uh oh!

elgnay commented Oct 28, 2025

Uh oh!

simonpasquier commented Oct 28, 2025

Uh oh!

simonpasquier commented Oct 28, 2025

Uh oh!

simonpasquier commented Oct 28, 2025

Uh oh!

openshift-ci-robot commented Oct 28, 2025

Uh oh!

simonpasquier commented Oct 28, 2025

Uh oh!

openshift-ci-robot commented Oct 28, 2025

Uh oh!

simonpasquier commented Oct 28, 2025

Uh oh!

simonpasquier commented Oct 28, 2025

Uh oh!

simonpasquier commented Oct 28, 2025

Uh oh!

openshift-ci-robot commented Oct 28, 2025

Uh oh!

openshift-ci bot commented Oct 28, 2025

Uh oh!

openshift-ci bot commented Oct 28, 2025

Uh oh!

openshift-ci bot commented Oct 28, 2025

Uh oh!

Uh oh!

openshift-ci-robot commented Oct 28, 2025

Uh oh!

elgnay commented Oct 20, 2025 •

edited

Loading