[K8s-R5.0]: Pod in Isolated namespace cannot resolve DNS request
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
Trunk |
Fix Released
|
Critical
|
Aniket Gawade |
Bug Description
Kubernetes
R5.0 (Mainline)
Issue observed post CB build 85
Ocata
Ubuntu16.04
Setup:
HA setup with 3 Control nodes. 1 Kube master
2 compute nodes
Issue:
Created 1 Isolated namespaces:
root@testbed-
Name: ctest-namespace
Labels: <none>
Annotations: opencontrail.
Status: Active
Created 1 Pod in the isolated namespace
ctest-namespace
Attempted to resolve DNS to kubernetes.
I was expecting it to resolve it correctly but it failed.
The issue has been introduced starting CB build 83.
On further debugging, found that the VN created on isolation of namespace does not have a route to DNS server 10.96.0.10.
There is no such route in VRF of the new VN corresponding to isolated namespace.
Changed in juniperopenstack: | |
assignee: | Sachchidanand Vaidya (vaidyasd) → Aniket Gawade (aniketgawade) |
Sanity test case that is failing due to this issue is : olated. test_kube_ dns_lookup
TestServiceVNIs