yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #10728
[Bug 1261007] Re: Nova Docker driver doesn't remove created network namespace
** Changed in: nova
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1261007
Title:
Nova Docker driver doesn't remove created network namespace
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
The Nova Docker driver doesn't remove the network namespace after
machine has been destroyed.
Steps to reproduce:
1. Look up available network namespaces, on a fresh machine the list should be empty:
$ ip netns show
2. Start a new docker container via nova
$ nova boot --image busybox:latest test1
3. Look up available network namespaces:
$ ip netns show
5f6b61d44ae15a77b277ebbf422fe88f369f8cdbb81a64aa6ea4beaf110204a6
4. Destroy nova instance
$ nova delete test1
5. Look up available network namespaces, the list must be empty but isn't
$ ip netns show
5f6b61d44ae15a77b277ebbf422fe88f369f8cdbb81a64aa6ea4beaf110204a6
The nova drive must remove this network namespaces on instance destroy by calling:
ip netns delete $container_id
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1261007/+subscriptions
References