Skip to content

NO-ISSUE: rebase-release-4.20-4.20.0-0.nightly-2025-11-22-184222_amd64-2025-11-22_arm64-2025-11-23#5792

Merged
openshift-merge-bot[bot] merged 5 commits intorelease-4.20from
rebase-release-4.20-4.20.0-0.nightly-2025-11-22-184222_amd64-2025-11-22_arm64-2025-11-23
Nov 25, 2025
Merged

NO-ISSUE: rebase-release-4.20-4.20.0-0.nightly-2025-11-22-184222_amd64-2025-11-22_arm64-2025-11-23#5792
openshift-merge-bot[bot] merged 5 commits intorelease-4.20from
rebase-release-4.20-4.20.0-0.nightly-2025-11-22-184222_amd64-2025-11-22_arm64-2025-11-23

Conversation

@microshift-rebase-script
Copy link
Contributor

@microshift-rebase-script microshift-rebase-script bot commented Nov 24, 2025

amd64: 4.20.0-0.nightly-2025-11-22-184222
arm64: 4.20.0-0.nightly-arm64-2025-11-23-231914
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.20-periodics-rebase-on-nightlies/1992805704167067648

  • machine-config-operator embedded-component 1f11aef23bd1a7d89fba38480451e2404e00f3a3 to 0a8e1230d454fb7d72f54bf9065db3a4769b9a86
    • e09a8aad 2025-11-19T15:59:17+00:00 remove --mount directives
    • 8f0b0a8a 2025-11-18T13:53:52+05:30 OCPNODE-3722: OCP 4.20 and earlier cluster should have AutoSizingReserved disable by default

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

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 24, 2025
@microshift-rebase-script
Copy link
Contributor Author

/verified by automatic-rebase

@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 24, 2025

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

Details

In response to this:

amd64: 4.20.0-0.nightly-2025-11-22-184222
arm64: 4.20.0-0.nightly-arm64-2025-11-23-231914
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.20-periodics-rebase-on-nightlies/1992805704167067648

  • machine-config-operator embedded-component 1f11aef23bd1a7d89fba38480451e2404e00f3a3 to 0a8e1230d454fb7d72f54bf9065db3a4769b9a86
  • e09a8aad 2025-11-19T15:59:17+00:00 remove --mount directives
  • 8f0b0a8a 2025-11-18T13:53:52+05:30 OCPNODE-3722: OCP 4.20 and earlier cluster should have AutoSizingReserved disable by default

/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. labels Nov 24, 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 added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Nov 24, 2025
@openshift-ci openshift-ci bot requested review from copejon and ggiguash November 24, 2025 04:34
@pmtk
Copy link
Member

pmtk commented Nov 24, 2025

/retest

Warning  FailedScheduling  60s   default-scheduler  0/1 nodes are available: 1 node(s) did not have enough free storage. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling

@pmtk
Copy link
Member

pmtk commented Nov 24, 2025

olm transient error

/retest

@pmtk
Copy link
Member

pmtk commented Nov 25, 2025

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 25, 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.

@pmtk
Copy link
Member

pmtk commented Nov 25, 2025

/lgtm
/verified by ci

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

@pmtk: This PR has been marked as verified by ci.

Details

In response to this:

/lgtm
/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-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 25, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 25, 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 Nov 25, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit dc50bdb into release-4.20 Nov 25, 2025
13 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.20-4.20.0-0.nightly-2025-11-22-184222_amd64-2025-11-22_arm64-2025-11-23 branch November 25, 2025 13:51
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.

2 participants