Skip to content

NO-ISSUE: rebase-release-4.20-4.20.0-0.nightly-2025-10-07-014413_amd64-2025-10-07_arm64-2025-10-07#5574

Closed
microshift-rebase-script[bot] wants to merge 4 commits intorelease-4.20from
rebase-release-4.20-4.20.0-0.nightly-2025-10-07-014413_amd64-2025-10-07_arm64-2025-10-07
Closed

NO-ISSUE: rebase-release-4.20-4.20.0-0.nightly-2025-10-07-014413_amd64-2025-10-07_arm64-2025-10-07#5574
microshift-rebase-script[bot] wants to merge 4 commits intorelease-4.20from
rebase-release-4.20-4.20.0-0.nightly-2025-10-07-014413_amd64-2025-10-07_arm64-2025-10-07

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 4.20.0-0.nightly-2025-10-07-014413
arm64: 4.20.0-0.nightly-arm64-2025-10-07-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/1975773320339001344

  • ovn-kubernetes image-arm64 74b1c90eb97bea68bf708d47f28fce7de9adc7b9 to 7b3e4fbdea6c5a384a82ceb3ca56b2074afca3cc
    • ba90f223 2025-09-29T17:47:06+02:00 Fix EgressIP controller deadlock by sorting node locks lexicographically

/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 Oct 8, 2025
@microshift-rebase-script
Copy link
Copy Markdown
Contributor Author

/verified by automatic-rebase

@openshift-ci-robot
Copy link
Copy Markdown

@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-07-014413
arm64: 4.20.0-0.nightly-arm64-2025-10-07-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/1975773320339001344

  • ovn-kubernetes image-arm64 74b1c90eb97bea68bf708d47f28fce7de9adc7b9 to 7b3e4fbdea6c5a384a82ceb3ca56b2074afca3cc
  • ba90f223 2025-09-29T17:47:06+02:00 Fix EgressIP controller deadlock by sorting node locks lexicographically

/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 8, 2025
@openshift-ci-robot
Copy link
Copy Markdown

@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 October 8, 2025 04:29
@pacevedom
Copy link
Copy Markdown
Contributor

/retest

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Oct 8, 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
Copy Markdown
Member

pmtk commented Oct 8, 2025

/lgtm

@pmtk
Copy link
Copy Markdown
Member

pmtk commented Oct 8, 2025

/verified by CI

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

@pmtk: 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-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 8, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Oct 8, 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 8, 2025
@pmtk
Copy link
Copy Markdown
Member

pmtk commented Oct 9, 2025

/close
in favor of #5583

@openshift-ci openshift-ci bot closed this Oct 9, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Oct 9, 2025

@pmtk: Closed this PR.

Details

In response to this:

/close
in favor of #5583

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.

@microshift-rebase-script microshift-rebase-script bot deleted the rebase-release-4.20-4.20.0-0.nightly-2025-10-07-014413_amd64-2025-10-07_arm64-2025-10-07 branch October 10, 2025 04:24
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