**FAILURE** rebase-4.15.0-0.nightly_amd64-2025-04-16-032433_arm64-2025-04-15-193250 - #4809
Conversation
|
[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. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/close |
|
@pmtk: Closed this PR. 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 kubernetes-sigs/prow repository. |
|
@microshift-rebase-script[bot]: The following test failed, say
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. |
rebase.sh failed - check committed rebase_sh.log
amd64: 4.15.0-0.nightly-2025-04-16-032433
arm64: 4.15.0-0.nightly-arm64-2025-04-15-193250
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1912717997315723264
cluster-network-operator embedded-component 20786bb70ae9a238f0673b3fbf1f90e25df659ab to e88176de7420cb92099445af4a81d7da48558bfd
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.machine-config-operator embedded-component d6c08256872b54e79fc00fa2c280b626d23bd276 to b23bb29eeffa659058ae6a88969cc0e6a97d82f5
ovn-kubernetes image-amd64 01af23cb323ec1506b5faf23e3e0d3b59df24fc8 to 1ba21a20c877b452d0b0c091644eb34ff60352fe
ovn-kubernetes image-arm64 01af23cb323ec1506b5faf23e3e0d3b59df24fc8 to 1ba21a20c877b452d0b0c091644eb34ff60352fe
/label tide/merge-method-squash
/label cherry-pick-approved
/label backport-risk-assessed
/label jira/valid-bug