Skip to content

NO-ISSUE: rebase-release-4.20-4.20.0-0.nightly-2025-10-05-124915_amd64-2025-10-05_arm64-2025-10-05#5559

Merged
openshift-merge-bot[bot] merged 4 commits intorelease-4.20from
rebase-release-4.20-4.20.0-0.nightly-2025-10-05-124915_amd64-2025-10-05_arm64-2025-10-05
Oct 6, 2025
Merged

NO-ISSUE: rebase-release-4.20-4.20.0-0.nightly-2025-10-05-124915_amd64-2025-10-05_arm64-2025-10-05#5559
openshift-merge-bot[bot] merged 4 commits intorelease-4.20from
rebase-release-4.20-4.20.0-0.nightly-2025-10-05-124915_amd64-2025-10-05_arm64-2025-10-05

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.20.0-0.nightly-2025-10-05-124915
arm64: 4.20.0-0.nightly-arm64-2025-10-05-192559
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.20-periodics-rebase-on-nightlies/1975048522520596480

  • machine-config-operator embedded-component d707114bc07c40c63084de0f91748b2efda91739 to 58f14fc5d33718cc2c6c38e51e05147a8303aba1
    • 941c3279 2025-10-02T13:57:21+00:00 certcontroller: update unit tests
    • 1203a83c 2025-10-02T13:57:21+00:00 certcontroller: resync on infra object
    • b9b69935 2025-09-24T17:26:15+00:00 controller: update is node done check to handle image mode disabling case & add unit test cases for scenario

/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 Oct 6, 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-10-05-124915
arm64: 4.20.0-0.nightly-arm64-2025-10-05-192559
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.20-periodics-rebase-on-nightlies/1975048522520596480

  • machine-config-operator embedded-component d707114bc07c40c63084de0f91748b2efda91739 to 58f14fc5d33718cc2c6c38e51e05147a8303aba1
  • 941c3279 2025-10-02T13:57:21+00:00 certcontroller: update unit tests
  • 1203a83c 2025-10-02T13:57:21+00:00 certcontroller: resync on infra object
  • b9b69935 2025-09-24T17:26:15+00:00 controller: update is node done check to handle image mode disabling case & add unit test cases for scenario

/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 Oct 6, 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 ggiguash and vanhalenar October 6, 2025 04:36
@pacevedom
Copy link
Contributor

/retest

@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 6, 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.

@pmtk
Copy link
Member

pmtk commented Oct 6, 2025

/lgtm

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

openshift-ci bot commented Oct 6, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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 6, 2025
@jerpeter1
Copy link
Member

/label staff-eng-approved

@openshift-ci openshift-ci bot added the staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). label Oct 6, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD d6de8bc and 2 for PR HEAD 15917b5 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 6, 2025

@microshift-rebase-script: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit 498172c into release-4.20 Oct 6, 2025
12 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.20-4.20.0-0.nightly-2025-10-05-124915_amd64-2025-10-05_arm64-2025-10-05 branch October 6, 2025 20:34
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. staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). 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.

4 participants