NO-ISSUE: rebase-release-4.18-4.18.0-0.nightly-2025-04-02-174719_amd64-2025-04-02_arm64-2025-04-02 - #4759
Conversation
|
@microshift-rebase-script[bot]: This pull request explicitly references no jira issue. DetailsIn response to this:
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. |
|
@microshift-rebase-script[bot]: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/lgtm |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
amd64: 4.18.0-0.nightly-2025-04-02-174719
arm64: 4.18.0-0.nightly-arm64-2025-04-02-182118
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.18-periodics-rebase-on-nightlies/1907644532682395648
cluster-ingress-operator embedded-component b0222ed2054e3ff7b87f4f90d72b42b6cf2b53a7 to d967a73c5f7da76783ee1af093f21817e7681e1d
cluster-network-operator embedded-component 8cbda2ddf6aef578ea40f224c1281c2a6ee262c4 to 670c2e35eb315547eceae8a3a1b6e19638ff4f44
status.MachineCount == status.UpdatedMachineCount && hasSourceInMachineConfigStatus(status, machineConfigs)is introduced with PR OCPBUGS-32525: Check every MachineConfigPool for IPsec plugin existence cluster-network-operator#2349 which ensures IPsec machine config is always installed on all the nodes in the cluster, So this is deleting the IPsec daemonset as per the CNO state machine for IPsec when the condition is not met. But this is also accidentally disabling IPsec in OVN which is not an expected behavior. This causes ovs-monitor-ipsec to refresh existing ipsec connections unnecessarily when IPsec pod comes up as it is not able to find remote_name from the tunnel. This may also trigger deleting IPsec connection entries from openshift.conf file if ovs-monitor-ipsec is not killed timely when ipsec daemonset is removed. So this commit enables ovn ipsec option as long as the API is set with Full mode.kubernetes embedded-component 6020cf5333bdeb77f95fa33f8272e5251ea28edc to 97471c6ac55733da63e4db6680889897a5915ca7
OrderedNamespaceDeletionfor apiserver.machine-config-operator embedded-component 805bc69d1d4adc10ab57fe0466eb7ab342e903af to 28740b628797734ed26d4b4926530f6d41d4ce6b
ovn-kubernetes image-amd64 799f96146c2056a50ae8252a87c03de1cc698f13
The change list was truncated. See scripts/auto-rebase/changelog.txt in the PR for the full details.
/label tide/merge-method-squash
/label cherry-pick-approved
/label backport-risk-assessed
/label jira/valid-bug