-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NO-ISSUE: rebase-main-4.19.0-0.nightly-2025-01-25-021606_amd64-2025-01-25_arm64-2025-01-25 #4470
base: main
Are you sure you want to change the base?
Conversation
@microshift-rebase-script[bot]: This pull request explicitly references no jira issue. In 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. |
Extra messages:
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: microshift-rebase-script[bot] The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
/retest |
@microshift-rebase-script[bot]: The following tests failed, say
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. |
amd64: 4.19.0-0.nightly-2025-01-25-021606
arm64: 4.19.0-0.nightly-arm64-2025-01-25-000530
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1883726970630443008
api embedded-component c21a6eb290e4c665e7c986b11657dee5d48a510e to a770960d61e0f5518549477e96ee4d1f5a8bc047
cluster-ingress-operator embedded-component 2856e6ddee396b3cb5492ac128c3015956651b51 to cba3e44da2e6b48bc84e80cd715d6637e2713368
cluster-kube-apiserver-operator embedded-component fef044da6d5f71c44327ff78fb64502f264acb00 to bb90f17b3978b41882ecb12e28d0012e8324d69a
cluster-kube-scheduler-operator embedded-component b1cc4471e2f6c5dc81b2b9471f4634f1ecdb88b4 to fcefcca15b1e7812f45bfeec10ee771011551635
cluster-network-operator embedded-component 0dfccc148f815b67cc472945d8d7aec68e0b6a74 to 51a6fc7c63b778f1d6640f6dbb0ebad9f1d4c078
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 4b2db1ec33faa3ffc305e5ffa7376908cc955370 to d6d0ba181b25cdd0db6ca436038fe39c90a58ac3
machine-config-operator embedded-component 11b9ad07624cf75365c7897b922a54716f1951e5 to 38fb1b8bd28da78a79bb96eb3c9e978bab2752ff
ovn-kubernetes image-amd64 cd2cd1bf1da301ac11aaa0b75b55966ff886d97a to fcf25ea44a89c3cd9d6a287a7e7b3f04fb1e36d7
kubernetes image-amd64 4b2db1ec33faa3ffc305e5ffa7376908cc955370 to d6d0ba181b25cdd0db6ca436038fe39c90a58ac3
ovn-kubernetes image-arm64 cd2cd1bf1da301ac11aaa0b75b55966ff886d97a to fcf25ea44a89c3cd9d6a287a7e7b3f04fb1e36d7
kubernetes image-arm64 4b2db1ec33faa3ffc305e5ffa7376908cc955370 to d6d0ba181b25cdd0db6ca436038fe39c90a58ac3
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