-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.14
-
None
-
No
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-19494. The following is the description of the original issue:
—
Description of problem:
ipsec container kills pluto even if that was started by systemd
Version-Release number of selected component (if applicable):
on any 4.14 nightly
How reproducible:
every time
Steps to Reproduce:
1. enable N-S ipsec 2. enable E-W IPsec 3. kill/stop/delete one of the ipsec-host pods
Actual results:
pluto is killed on that host
Expected results:
pluto keeps running
Additional info:
https://github.com/yuvalk/cluster-network-operator/blob/37d1cc72f4f6cd999046bd487a705e6da31301a5/bindata/network/ovn-kubernetes/common/ipsec-host.yaml#L235 this should be removed
- clones
-
OCPBUGS-19494 when ovn ipsec pod stop/restart it kills pluto preventing further IPsec IKE communication
- Closed
- is blocked by
-
OCPBUGS-19494 when ovn ipsec pod stop/restart it kills pluto preventing further IPsec IKE communication
- Closed
- is duplicated by
-
OCPBUGS-19687 when ovn ipsec pod stop/restart it kills pluto preventing further IPsec IKE communication
- Closed
- links to
-
RHSA-2023:5006 OpenShift Container Platform 4.14.z security update