Namespaces isolation is not working with new agent bin in 5.0 build 132
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-
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-
[root@ip-
[root@ip-
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-
[root@ip-
[root@ip-
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.
[root@ip-
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 |