Nova Docker driver doesn't remove created network namespace
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Daniel Kuffner |
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
5f6b61d44ae
4. Destroy nova instance
$ nova delete test1
5. Look up available network namespaces, the list must be empty but isn't
$ ip netns show
5f6b61d44ae
The nova drive must remove this network namespaces on instance destroy by calling:
ip netns delete $container_id
Changed in nova: | |
assignee: | nobody → Daniel Kuffner (daniel-kuffner) |
Changed in nova: | |
importance: | Undecided → Medium |
Changed in nova: | |
milestone: | none → icehouse-3 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | icehouse-3 → 2014.1 |
Fix proposed to branch: master /review. openstack. org/62183
Review: https:/