Namespaces isolation is not working with new agent bin in 5.0 build 132

Bug #1752689 reported by Savithru Lokanath
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
New
Undecided
Naveen N

Bug Description

With the new agent bin provided by Naveen, noticed that namespace isolation doesn't seem work. Naveen to talk with Yuvaraja & come up with a solution.

[root@ip-10-0-10-100 policy]# oc get pods -o wide -n demo
NAME READY STATUS RESTARTS AGE IP NODE
testapp 1/1 Running 0 18h 10.47.255.249 ip-10-0-10-200
ubuntuapp 1/1 Running 0 1m 10.47.255.248 ip-10-0-10-200
webapp 1/1 Running 0 18h 10.47.255.251 ip-10-0-10-200
[root@ip-10-0-10-100 policy]#
[root@ip-10-0-10-100 policy]#
[root@ip-10-0-10-100 policy]# oc get pods -o wide -n isolated-ns
NAME READY STATUS RESTARTS AGE IP NODE
ubuntuapp-isolated 1/1 Running 0 30s 10.47.255.247 ip-10-0-10-200
[root@ip-10-0-10-100 policy]#
[root@ip-10-0-10-100 policy]#
[root@ip-10-0-10-100 policy]# oc exec -it ubuntuapp ping 10.47.255.247 -n demo
PING 10.47.255.247 (10.47.255.247) 56(84) bytes of data.
64 bytes from 10.47.255.247: icmp_seq=1 ttl=63 time=0.575 ms
64 bytes from 10.47.255.247: icmp_seq=2 ttl=63 time=0.086 ms
64 bytes from 10.47.255.247: icmp_seq=3 ttl=63 time=0.055 ms
^C
--- 10.47.255.247 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.055/0.238/0.575/0.238 ms
[root@ip-10-0-10-100 policy]#

Tags: blocker csg
summary: - Namespaces isolation is not working in 5.0 build 132
+ Namespaces isolation is not working with new agent bin in 5.0 build 132
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.