-
Bug
-
Resolution: Done
-
Major
-
None
-
4.15
-
None
-
None
-
OSDOCS Sprint 261
-
1
-
False
-
-
-
Known Issue
-
In Progress
Description of problem:
Cause: During 4.14 to 4.15 IPsec upgrade, there are two occasions cluster nodes get rebooted which causes IPsec pod also get restarted, This causes IPsec SA is not established between some nodes. This may happen on a freshly installed >=4.15 cluster as well when IPsec pods are restarted. Consequence: Since IPsec SA is not established between nodes, pod to pod communication is completely broken between those nodes because pod traffic flows over via IPsec tunnel. Fix We are actively working to find out root cause and providing resolution for the problem.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- links to
(1 links to)