Skip to content

NO-ISSUE: rebase-release-4.20-4.20.0-0.nightly-2025-10-30-114955_amd64-2025-10-30_arm64-2025-10-30#5681

Merged
openshift-merge-bot[bot] merged 5 commits intorelease-4.20from
rebase-release-4.20-4.20.0-0.nightly-2025-10-30-114955_amd64-2025-10-30_arm64-2025-10-30
Oct 31, 2025
Merged

NO-ISSUE: rebase-release-4.20-4.20.0-0.nightly-2025-10-30-114955_amd64-2025-10-30_arm64-2025-10-30#5681
openshift-merge-bot[bot] merged 5 commits intorelease-4.20from
rebase-release-4.20-4.20.0-0.nightly-2025-10-30-114955_amd64-2025-10-30_arm64-2025-10-30

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.20.0-0.nightly-2025-10-30-114955
arm64: 4.20.0-0.nightly-arm64-2025-10-30-111415
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.20-periodics-rebase-on-nightlies/1984108343362326528

  • kubernetes embedded-component e0d42164c84ee27644b85a1d2c9bbb062066056d to debdebd535dc3f5d0ab3557aa79172ff92344d97

    • 87e4cfbe4 2025-10-28T17:17:49-04:00 UPSTREAM: : Skip CPU resource status for workload-pinned pods
  • ovn-kubernetes image-amd64 050ed2c215b55aef456c73c5217427600756ae75 to 73fbb3d0bb633723932a2930053360720a4f0f6c

    • 90fa4bb9 2025-10-28T13:41:43+01:00 Skip Pending pods in EgressIP status updates
  • kubernetes image-amd64 e0d42164c84ee27644b85a1d2c9bbb062066056d to debdebd535dc3f5d0ab3557aa79172ff92344d97

    • 87e4cfbe4 2025-10-28T17:17:49-04:00 UPSTREAM: : Skip CPU resource status for workload-pinned pods
  • ovn-kubernetes image-arm64 050ed2c215b55aef456c73c5217427600756ae75 to 73fbb3d0bb633723932a2930053360720a4f0f6c

    • 90fa4bb9 2025-10-28T13:41:43+01:00 Skip Pending pods in EgressIP status updates
  • kubernetes image-arm64 e0d42164c84ee27644b85a1d2c9bbb062066056d to debdebd535dc3f5d0ab3557aa79172ff92344d97

    • 87e4cfbe4 2025-10-28T17:17:49-04:00 UPSTREAM: : Skip CPU resource status for workload-pinned pods

/label tide/merge-method-squash
/label backport-risk-assessed
/label jira/valid-bug

@microshift-rebase-script
Copy link
Contributor Author

/verified by automatic-rebase

@openshift-ci-robot
Copy link

@microshift-rebase-script[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

amd64: 4.20.0-0.nightly-2025-10-30-114955
arm64: 4.20.0-0.nightly-arm64-2025-10-30-111415
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.20-periodics-rebase-on-nightlies/1984108343362326528

  • kubernetes embedded-component e0d42164c84ee27644b85a1d2c9bbb062066056d to debdebd535dc3f5d0ab3557aa79172ff92344d97

  • 87e4cfbe4 2025-10-28T17:17:49-04:00 UPSTREAM: : Skip CPU resource status for workload-pinned pods

  • ovn-kubernetes image-amd64 050ed2c215b55aef456c73c5217427600756ae75 to 73fbb3d0bb633723932a2930053360720a4f0f6c

  • 90fa4bb9 2025-10-28T13:41:43+01:00 Skip Pending pods in EgressIP status updates

  • kubernetes image-amd64 e0d42164c84ee27644b85a1d2c9bbb062066056d to debdebd535dc3f5d0ab3557aa79172ff92344d97

  • 87e4cfbe4 2025-10-28T17:17:49-04:00 UPSTREAM: : Skip CPU resource status for workload-pinned pods

  • ovn-kubernetes image-arm64 050ed2c215b55aef456c73c5217427600756ae75 to 73fbb3d0bb633723932a2930053360720a4f0f6c

  • 90fa4bb9 2025-10-28T13:41:43+01:00 Skip Pending pods in EgressIP status updates

  • kubernetes image-arm64 e0d42164c84ee27644b85a1d2c9bbb062066056d to debdebd535dc3f5d0ab3557aa79172ff92344d97

  • 87e4cfbe4 2025-10-28T17:17:49-04:00 UPSTREAM: : Skip CPU resource status for workload-pinned pods

/label tide/merge-method-squash
/label backport-risk-assessed
/label jira/valid-bug

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-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 31, 2025
@openshift-ci openshift-ci bot added tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Oct 31, 2025
@openshift-ci-robot
Copy link

@microshift-rebase-script[bot]: Jira verification commands are restricted to collaborators for this repo.

Details

In response to this:

/verified by automatic-rebase

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 dhensel-rh and pmtk October 31, 2025 04:27
@pacevedom
Copy link
Contributor

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 31, 2025

@microshift-rebase-script[bot]: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@eslutsky
Copy link
Contributor

/lgtm

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

openshift-ci bot commented Oct 31, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eslutsky, microshift-rebase-script[bot]

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

The pull request process is described here

Details 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 Oct 31, 2025
@pacevedom
Copy link
Contributor

/verified by CI

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

@pacevedom: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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-merge-bot openshift-merge-bot bot merged commit f15105c into release-4.20 Oct 31, 2025
13 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.20-4.20.0-0.nightly-2025-10-30-114955_amd64-2025-10-30_arm64-2025-10-30 branch October 31, 2025 11:23
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. 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. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants