Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: None
Affects Version/s: 4.15
Component/s: Documentation / SDN
Labels:
None

Regression:
None
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Release Note Text:

Hide
During an upgrade from 4.14 to 4.15, cluster nodes are rebooted and IPsec pods are restarted. There is currently a known issue that is causing the restarted IPsec pods to not establish IPsec security association (SA). As a consequence, pod-to-pod communication is broken between nodes in which the pod traffic flows over the IPsec tunnel. This happens on both newly installed 4.15 clusters, during the upgrade process from 4.14 to 4.15, as well as when IPsec pods are restarted.

Show
During an upgrade from 4.14 to 4.15, cluster nodes are rebooted and IPsec pods are restarted. There is currently a known issue that is causing the restarted IPsec pods to not establish IPsec security association (SA). As a consequence, pod-to-pod communication is broken between nodes in which the pod traffic flows over the IPsec tunnel. This happens on both newly installed 4.15 clusters, during the upgrade process from 4.14 to 4.15, as well as when IPsec pods are restarted.
Release Note Type:
Known Issue
Release Note Status:
In Progress

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

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: