4d72093de5
It seems confusing netns with pidns. Although 'ip netns exec' doesn't make sense, 'ip netns exec <netns> kill <pid>' itself success as expected. But as side effects, dentry of /proc/<pid>/ns/net becomes young, which increases the possibility to fail to delete netns. That's not good. Fixes: Bug #1158589 Change-Id: I9aa717ccb86d8bf00bb1e707d39bfb65d043532b Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
# -- Welcome! You have come across a cloud computing network fabric controller. It has identified itself as "Quantum." It aims to tame your (cloud) networking! # -- External Resources: The homepage for Quantum is: http://launchpad.net/quantum . Use this site for asking for help, and filing bugs. Code is available on github at <http://github.com/openstack/quantum>. The latest and most in-depth documentation on how to use Quantum is available at: <http://docs.openstack.org>. This includes: Quantum Administrator Guide http://docs.openstack.org/trunk/openstack-network/admin/content/ Quantum API Reference: http://docs.openstack.org/api/openstack-network/2.0/content/ The start of some developer documentation is available at: http://wiki.openstack.org/QuantumDevelopment For help using or hacking on Quantum, you can send mail to <mailto:openstack-dev@lists.openstack.org>.