Skip to content

NO-ISSUE: rebase-release-4.18-4.18.0-0.nightly-2025-11-16-173230_amd64-2025-11-16_arm64-2025-11-17#5748

Merged
openshift-merge-bot[bot] merged 5 commits intorelease-4.18from
rebase-release-4.18-4.18.0-0.nightly-2025-11-16-173230_amd64-2025-11-16_arm64-2025-11-17
Nov 17, 2025
Merged

NO-ISSUE: rebase-release-4.18-4.18.0-0.nightly-2025-11-16-173230_amd64-2025-11-16_arm64-2025-11-17#5748
openshift-merge-bot[bot] merged 5 commits intorelease-4.18from
rebase-release-4.18-4.18.0-0.nightly-2025-11-16-173230_amd64-2025-11-16_arm64-2025-11-17

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 4.18.0-0.nightly-2025-11-16-173230
arm64: 4.18.0-0.nightly-arm64-2025-11-17-034615
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.18-periodics-rebase-on-nightlies/1990269032082706432

  • ovn-kubernetes image-amd64 2fe096327a6da6602c509d108ea0ed4a599a7eb3 to 9f04906c9822218d53f51b1e4311f6590eca1db8

    • 3a524b55 2025-11-07T13:27:01+01:00 Fix cleanup of LRP for deleted pods
    • 6cd0f090 2025-11-07T13:27:01+01:00 Handle missing pod delete event in EIP controller
    • 75f0b7e9 2025-11-07T13:27:01+01:00 EgressIP: fix failover and restart stale SNAT/LRP; ensure status sync
    • 947941b7 2025-11-07T13:27:01+01:00 OVN EIP: fix printing of stale next hops value
    • 7b12cc64 2025-11-07T13:27:01+01:00 OVN EIP: add UT for syncing next hops for v4/v6
    • b7d8695b 2025-11-07T13:27:01+01:00 EIP: do not skip generating potential valid next hops if LSP not found
    • 87005cd4 2025-11-07T13:27:01+01:00 EIP: when checking for stale LRP next hops on startup, restrict to enodes
    • d5490685 2025-11-07T09:07:14+00:00 Reintroduce completed pod check in shouldReleaseDeletedPod
    • b170a2f2 2025-11-07T09:07:14+00:00 kubevirt: test with per-pod SNATs
    • d16ed585 2025-11-07T09:07:14+00:00 kubevirt: test OVN DB after completion of source pod
    • 9319b6d7 2025-11-07T09:07:14+00:00 kubevirt: fix search of colliding pods for migrated pods
    • 1b1515cc 2025-11-07T09:07:14+00:00 kubevirt: prevent error log on IP release
    • d077b268 2025-11-07T09:07:13+00:00 kubevirt: fix bad release of IPs of live migratable pods
    • e7bf7330 2025-11-07T09:07:13+00:00 kubevirt e2e: use a value for vm nodeselector
    • bc5438ca 2025-11-07T09:07:13+00:00 Fix naming of "Secondary" to be "User-Defined"
  • ovn-kubernetes image-arm64 672e10d79b520bee9a715ff07d46702e56ede51b to 9f04906c9822218d53f51b1e4311f6590eca1db8

    • 3a524b55 2025-11-07T13:27:01+01:00 Fix cleanup of LRP for deleted pods
    • 6cd0f090 2025-11-07T13:27:01+01:00 Handle missing pod delete event in EIP controller
    • 75f0b7e9 2025-11-07T13:27:01+01:00 EgressIP: fix failover and restart stale SNAT/LRP; ensure status sync
    • 947941b7 2025-11-07T13:27:01+01:00 OVN EIP: fix printing of stale next hops value
    • 7b12cc64 2025-11-07T13:27:01+01:00 OVN EIP: add UT for syncing next hops for v4/v6
    • b7d8695b 2025-11-07T13:27:01+01:00 EIP: do not skip generating potential valid next hops if LSP not found
    • 87005cd4 2025-11-07T13:27:01+01:00 EIP: when checking for stale LRP next hops on startup, restrict to enodes

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

@microshift-rebase-script
Copy link
Copy Markdown
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 Nov 17, 2025
@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.18.0-0.nightly-2025-11-16-173230
arm64: 4.18.0-0.nightly-arm64-2025-11-17-034615
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.18-periodics-rebase-on-nightlies/1990269032082706432

  • ovn-kubernetes image-amd64 2fe096327a6da6602c509d108ea0ed4a599a7eb3 to 9f04906c9822218d53f51b1e4311f6590eca1db8

  • 3a524b55 2025-11-07T13:27:01+01:00 Fix cleanup of LRP for deleted pods

  • 6cd0f090 2025-11-07T13:27:01+01:00 Handle missing pod delete event in EIP controller

  • 75f0b7e9 2025-11-07T13:27:01+01:00 EgressIP: fix failover and restart stale SNAT/LRP; ensure status sync

  • 947941b7 2025-11-07T13:27:01+01:00 OVN EIP: fix printing of stale next hops value

  • 7b12cc64 2025-11-07T13:27:01+01:00 OVN EIP: add UT for syncing next hops for v4/v6

  • b7d8695b 2025-11-07T13:27:01+01:00 EIP: do not skip generating potential valid next hops if LSP not found

  • 87005cd4 2025-11-07T13:27:01+01:00 EIP: when checking for stale LRP next hops on startup, restrict to enodes

  • d5490685 2025-11-07T09:07:14+00:00 Reintroduce completed pod check in shouldReleaseDeletedPod

  • b170a2f2 2025-11-07T09:07:14+00:00 kubevirt: test with per-pod SNATs

  • d16ed585 2025-11-07T09:07:14+00:00 kubevirt: test OVN DB after completion of source pod

  • 9319b6d7 2025-11-07T09:07:14+00:00 kubevirt: fix search of colliding pods for migrated pods

  • 1b1515cc 2025-11-07T09:07:14+00:00 kubevirt: prevent error log on IP release

  • d077b268 2025-11-07T09:07:13+00:00 kubevirt: fix bad release of IPs of live migratable pods

  • e7bf7330 2025-11-07T09:07:13+00:00 kubevirt e2e: use a value for vm nodeselector

  • bc5438ca 2025-11-07T09:07:13+00:00 Fix naming of "Secondary" to be "User-Defined"

  • ovn-kubernetes image-arm64 672e10d79b520bee9a715ff07d46702e56ede51b to 9f04906c9822218d53f51b1e4311f6590eca1db8

  • 3a524b55 2025-11-07T13:27:01+01:00 Fix cleanup of LRP for deleted pods

  • 6cd0f090 2025-11-07T13:27:01+01:00 Handle missing pod delete event in EIP controller

  • 75f0b7e9 2025-11-07T13:27:01+01:00 EgressIP: fix failover and restart stale SNAT/LRP; ensure status sync

  • 947941b7 2025-11-07T13:27:01+01:00 OVN EIP: fix printing of stale next hops value

  • 7b12cc64 2025-11-07T13:27:01+01:00 OVN EIP: add UT for syncing next hops for v4/v6

  • b7d8695b 2025-11-07T13:27:01+01:00 EIP: do not skip generating potential valid next hops if LSP not found

  • 87005cd4 2025-11-07T13:27:01+01:00 EIP: when checking for stale LRP next hops on startup, restrict to enodes

/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 Nov 17, 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 dhensel-rh and jogeo November 17, 2025 04:19
@openshift-ci
Copy link
Copy Markdown
Contributor

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

@pacevedom
Copy link
Copy Markdown
Contributor

/verified by CI

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

@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
Copy Markdown
Member

pmtk commented Nov 17, 2025

/lgtm

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

openshift-ci bot commented Nov 17, 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 17, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 87ec14b into release-4.18 Nov 17, 2025
13 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.18-4.18.0-0.nightly-2025-11-16-173230_amd64-2025-11-16_arm64-2025-11-17 branch November 17, 2025 13:52
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