Skip to content

NO-ISSUE: rebase-release-4.20-4.20.0-0.nightly-2025-12-02-131357_amd64-2025-12-02_arm64-2025-12-04#5855

Merged
openshift-merge-bot[bot] merged 4 commits intorelease-4.20from
rebase-release-4.20-4.20.0-0.nightly-2025-12-02-131357_amd64-2025-12-02_arm64-2025-12-04
Dec 5, 2025
Merged

NO-ISSUE: rebase-release-4.20-4.20.0-0.nightly-2025-12-02-131357_amd64-2025-12-02_arm64-2025-12-04#5855
openshift-merge-bot[bot] merged 4 commits intorelease-4.20from
rebase-release-4.20-4.20.0-0.nightly-2025-12-02-131357_amd64-2025-12-02_arm64-2025-12-04

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.20.0-0.nightly-2025-12-02-131357
arm64: 4.20.0-0.nightly-arm64-2025-12-04-031946
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.20-periodics-rebase-on-nightlies/1996429491135582208

  • cluster-network-operator embedded-component 45843d223ceaea458879da3ee58d89ce1863230b to 8f216c0de0807e9a256aef6020d9f0a39cfff817

    • 23e7363 2025-11-13T11:01:09+00:00 Preserve custom resource requests on ovn-control-plane pods
  • machine-config-operator embedded-component 0a8e1230d454fb7d72f54bf9065db3a4769b9a86 to 5fe9249e195b76d4e2482cbd5d3e50b848b9a3f5

    • aa13e2db 2025-11-21T15:53:16-05:00 check ClusterImagePolicy conflicts only on default clusters

/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 openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 4, 2025
@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-12-02-131357
arm64: 4.20.0-0.nightly-arm64-2025-12-04-031946
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.20-periodics-rebase-on-nightlies/1996429491135582208

  • cluster-network-operator embedded-component 45843d223ceaea458879da3ee58d89ce1863230b to 8f216c0de0807e9a256aef6020d9f0a39cfff817

  • 23e7363 2025-11-13T11:01:09+00:00 Preserve custom resource requests on ovn-control-plane pods

  • machine-config-operator embedded-component 0a8e1230d454fb7d72f54bf9065db3a4769b9a86 to 5fe9249e195b76d4e2482cbd5d3e50b848b9a3f5

  • aa13e2db 2025-11-21T15:53:16-05:00 check ClusterImagePolicy conflicts only on default clusters

/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 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 Dec 4, 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 agullon and jerpeter1 December 4, 2025 04:15
@pmtk
Copy link
Member

pmtk commented Dec 4, 2025

/retest

1 similar comment
@pmtk
Copy link
Member

pmtk commented Dec 4, 2025

/retest

@pacevedom
Copy link
Contributor

/test e2e-aws-tests-bootc

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 4, 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.

Copy link
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

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

/lgtm
/verified by CI

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

openshift-ci bot commented Dec 5, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Dec 5, 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 Dec 5, 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 b1ffd42 into release-4.20 Dec 5, 2025
12 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.20-4.20.0-0.nightly-2025-12-02-131357_amd64-2025-12-02_arm64-2025-12-04 branch December 5, 2025 06:50
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