Comment 6 for bug 1405293

So the fact that namespace itself still there doesn't bothering you ? ;)
 On Feb 20, 2015 11:35 AM, "Daniel Shafer" <email address hidden> wrote:

> This bug is invalid for 6.0.1.
>
> Namespace on node-1 before killing network:
>
> [root@node-1 ~]# ip netns exec
> qrouter-33debcd2-8f98-4893-80e0-9fc1669f9bdd ifconfig
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:65536 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> qg-2fc9d393-8d Link encap:Ethernet HWaddr FA:16:3E:75:E9:65
> inet addr:10.108.21.130 Bcast:10.108.21.255 Mask:255.255.255.0
> inet6 addr: fe80::f816:3eff:fe75:e965/64 Scope:Link
> UP BROADCAST RUNNING MTU:1500 Metric:1
> RX packets:64 errors:0 dropped:0 overruns:0 frame:0
> TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:4024 (3.9 KiB) TX bytes:1216 (1.1 KiB)
>
> qr-43142bdd-7c Link encap:Ethernet HWaddr FA:16:3E:11:EA:70
> inet addr:192.168.111.1 Bcast:192.168.111.255
> Mask:255.255.255.0
> inet6 addr: fe80::f816:3eff:fe11:ea70/64 Scope:Link
> UP BROADCAST RUNNING MTU:1500 Metric:1
> RX packets:1 errors:0 dropped:0 overruns:0 frame:0
> TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:70 (70.0 b) TX bytes:794 (794.0 b)
>
> After network was brought back up on node-1:
>
> [root@node-1 init.d]# ip netns exec
> qrouter-33debcd2-8f98-4893-80e0-9fc1669f9bdd ifconfig
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:65536 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1405293
>
> Title:
> Neutron agents previous envs not cleaned up on migration
>
> Status in Fuel: OpenStack installer that works:
> Invalid
> Status in Fuel for OpenStack 5.0.x series:
> Confirmed
> Status in Fuel for OpenStack 5.1.x series:
> Confirmed
> Status in Fuel for OpenStack 6.0.x series:
> Confirmed
>
> Bug description:
> So I found that if we have some of neutron agents (like l3 or dhcp)
> migrated to the different node their childs/namespaces and so on not
> cleared up on previous node. That is very dangerous behaviour because
> of l3 it will leave namespaces with routes and in case of dhcp it will
> leave a lot of namespaces and dnsmasq's on previous node.
>
> ocf scripts should do a cleanup on all the nodes and only after that
> start migrated agent on new node.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/fuel/+bug/1405293/+subscriptions
>