[Openshift/K8S] : When configuring SNAT router host losing connectivity
Bug #1735590 reported by
chhandak
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R4.1 |
Fix Committed
|
High
|
Yuvaraja Mariappan | |||
R5.0 |
Fix Committed
|
High
|
Yuvaraja Mariappan | |||
Trunk |
Fix Committed
|
High
|
Yuvaraja Mariappan |
Bug Description
When we crate SNAT router and extend cluster-network to that SNAT router host is losing all connectivity.
In 4.1 kube-manager create a policy between IP Fabric network and cluster network by default. Now while extending this to a SNAT router all underlay traffic is dropped. Host is losing connectivity
Workaround: Disassociating ip-fabric-
Changed in juniperopenstack: | |
importance: | Undecided → High |
assignee: | nobody → Sachchidanand Vaidya (vaidyasd) |
milestone: | none → r4.1.0.0-fcs |
information type: | Proprietary → Public |
summary: |
- [Openshift] : When configuring SNAT router host loosing connectivity + [Openshift/K8S] : When configuring SNAT router host loosing + connectivity |
summary: |
- [Openshift/K8S] : When configuring SNAT router host loosing + [Openshift/K8S] : When configuring SNAT router host losing connectivity |
To post a comment you must log in.
Releasenotes:
In Kubernetes and Openshift based deployments when we crate SNAT router and extend cluster-network to that SNAT router host is losing all connectivity.
Workaround: Disassociating ip-fabric- cluster- network- default policy and delete the same solves the problem. So if SNAT feature has to be used in contrail first ip-fabric- cluster- network- default policy should be disassociated and deleted