Skip to content

Conversation

@rphillips
Copy link

@rphillips rphillips commented Aug 6, 2025

test: add retry to getMetricsFromNode and deflake 'should grab all metrics from kubelet /metrics/resource endpoint

Upstream 1.34 PR: kubernetes#133392

@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Aug 6, 2025
@openshift-ci-robot
Copy link

@rphillips: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@rphillips
Copy link
Author

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-gcp-ovn-rt 7

@openshift-ci
Copy link

openshift-ci bot commented Aug 6, 2025

@rphillips: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-gcp-ovn-rt

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ac0763f0-72e8-11f0-8620-33f6ad498d1d-0

@openshift-ci openshift-ci bot requested review from deads2k and jerpeter1 August 6, 2025 17:14
@rphillips
Copy link
Author

/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade 7
/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-gcp-ovn-rt 7
/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade 7

@openshift-ci
Copy link

openshift-ci bot commented Aug 7, 2025

@rphillips: trigger 3 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.20-e2e-gcp-ovn-rt
  • periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ffd7a410-7322-11f0-936c-d273dfe2e028-0

@rphillips
Copy link
Author

/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-upgrade 7

@openshift-ci
Copy link

openshift-ci bot commented Aug 7, 2025

@rphillips: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8ea4b1f0-7388-11f0-8d7a-6b5c040c8979-0

@rphillips
Copy link
Author

/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade 7
/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-gcp-ovn-rt 7
/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade 7

@openshift-ci
Copy link

openshift-ci bot commented Aug 7, 2025

@rphillips: trigger 3 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.20-e2e-gcp-ovn-rt
  • periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-aws-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/06fc0240-738c-11f0-8890-57ff9f228409-0

@bitoku
Copy link

bitoku commented Aug 7, 2025

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-gcp-ovn-runc-techpreview 10
/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview 10

@openshift-ci
Copy link

openshift-ci bot commented Aug 7, 2025

@bitoku: trigger 2 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-gcp-ovn-runc-techpreview
  • periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/645d9970-73a1-11f0-9c13-142bda26f12b-0

@rphillips
Copy link
Author

/retest

@rphillips rphillips changed the title UPSTREAM: 133392: test: add retry to getMetricsFromNode UPSTREAM: carry: test: add retry to getMetricsFromNode Aug 14, 2025
@openshift-ci-robot
Copy link

@rphillips: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@rphillips
Copy link
Author

/retest

@rphillips rphillips changed the title UPSTREAM: carry: test: add retry to getMetricsFromNode OCPBUGS-57477: UPSTREAM: carry: test: add retry to getMetricsFromNode Aug 19, 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 Aug 19, 2025
@openshift-ci-robot
Copy link

@rphillips: This pull request references Jira Issue OCPBUGS-57477, 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.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

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

In response to this:

test: add retry to getMetricsFromNode and deflake 'should grab all metrics from kubelet /metrics/resource endpoint

Upstream 1.34 PR: kubernetes#133392

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/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Aug 19, 2025
@rphillips rphillips changed the title OCPBUGS-57477: UPSTREAM: carry: test: add retry to getMetricsFromNode OCPBUGS-57477: UPSTREAM: 133392: test: add retry to getMetricsFromNode Nov 6, 2025
@openshift-ci-robot openshift-ci-robot added backports/validated-commits Indicates that all commits come to merged upstream PRs. and removed backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. labels Nov 6, 2025
@openshift-ci-robot
Copy link

@rphillips: the contents of this pull request could be automatically validated.

The following commits are valid:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci
Copy link

openshift-ci bot commented Nov 7, 2025

@rphillips: The following tests 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/okd-scos-e2e-aws-ovn 7fc7c74 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-techpreview-serial 7fc7c74 link false /test e2e-aws-ovn-techpreview-serial
ci/prow/e2e-aws-ovn-serial 7fc7c74 link true /test e2e-aws-ovn-serial

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.

@rphillips
Copy link
Author

/retest

@harche
Copy link

harche commented Nov 7, 2025

/lgtm

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

tkashem commented Nov 7, 2025

/approve

@openshift-ci
Copy link

openshift-ci bot commented Nov 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: harche, rphillips, tkashem

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 7, 2025
@rphillips
Copy link
Author

/verified by @rphillips

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

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

In response to this:

/verified by @rphillips

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

/retest-required

Remaining retests: 0 against base HEAD 6681e18 and 2 for PR HEAD cd7a7f1 in total

@openshift-merge-bot openshift-merge-bot bot merged commit 891f5bb into openshift:master Nov 8, 2025
23 checks passed
@openshift-ci-robot
Copy link

@rphillips: Jira Issue OCPBUGS-57477: Some pull requests linked via external trackers have merged:

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

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-57477 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:

test: add retry to getMetricsFromNode and deflake 'should grab all metrics from kubelet /metrics/resource endpoint

Upstream 1.34 PR: kubernetes#133392

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.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/validated-commits Indicates that all commits come to merged upstream PRs. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants