Skip to content

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.18.0-0.nightly-2025-11-09-205422
arm64: 4.18.0-0.nightly-arm64-2025-11-10-013203
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.18-periodics-rebase-on-nightlies/1987732399861010432

  • api embedded-component 98e18dae8c7a82a4075c65ca0d357c9bf31cfb7c to 28db677d74623ae691400619565d01b7a5818601

    • a0eb693 2025-11-03T12:56:45-05:00 Promote streaming list encoding to Default on Hypershift.
  • oc image-amd64 4fcb2d07875f05d881ac90af73723db0ae5b1d6e to 03e97ec079064c4f451b15510622caac316fb517

    • 9d80b182 2025-11-03T17:56:30+00:00 Prefer ready and reachable control plane nodes
    • bd8e87d3 2025-11-03T17:56:30+00:00 Filter out unreachable taints from tolerations

/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 10, 2025
@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.

In response to this:

amd64: 4.18.0-0.nightly-2025-11-09-205422
arm64: 4.18.0-0.nightly-arm64-2025-11-10-013203
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.18-periodics-rebase-on-nightlies/1987732399861010432

  • api embedded-component 98e18dae8c7a82a4075c65ca0d357c9bf31cfb7c to 28db677d74623ae691400619565d01b7a5818601

  • a0eb693 2025-11-03T12:56:45-05:00 Promote streaming list encoding to Default on Hypershift.

  • oc image-amd64 4fcb2d07875f05d881ac90af73723db0ae5b1d6e to 03e97ec079064c4f451b15510622caac316fb517

  • 9d80b182 2025-11-03T17:56:30+00:00 Prefer ready and reachable control plane nodes

  • bd8e87d3 2025-11-03T17:56:30+00:00 Filter out unreachable taints from tolerations

/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 the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Nov 10, 2025
@openshift-ci-robot
Copy link

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

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 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 Nov 10, 2025
@openshift-ci openshift-ci bot requested review from copejon and jerpeter1 November 10, 2025 04:20
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 10, 2025

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

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.

@eslutsky
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 10, 2025
@eslutsky
Copy link
Contributor

/lgtm

@openshift-ci
Copy link
Contributor

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

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

@eslutsky
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 Nov 10, 2025
@openshift-ci-robot
Copy link

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

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 6c10c2a into release-4.18 Nov 10, 2025
12 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.18-4.18.0-0.nightly-2025-11-09-205422_amd64-2025-11-09_arm64-2025-11-10 branch November 10, 2025 13:45
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