yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1460681@xxxxxxxxxxxxxxxxxx>]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1460681

Title:
  Neutron DHCP namespaces are not created properly on reboot

Status in neutron:
  Expired

Bug description:
  I am running a Openstack Juno on a bunch of docker containers. When my
  neutron-network container reboots, neutron dhcp logs has a bunch of

  015-05-28 17:49:14.629 475 TRACE neutron.agent.dhcp_agent Stderr:
  'RTNETLINK answers: Invalid argument\n' 2015-05-28 17:49:14.629 475
  TRACE neutron.agent.dhcp_agent

  I noticed that this is due to the fact that the namespace behaves
  weird when the container comes back up:

  # ip netns exec qdhcp-474bd6da-e74f-436a-8408-e10fe5925220 ip a
  setting the network namespace
  "qdhcp-474bd6da-e74f-436a-8408-e10fe5925220" failed: Invalid argument
  # ls -la /var/run/netns/
  total 8
  drwxr-xr-x 2 root root 4096 May 29 14:43 .
  drwxr-xr-x 9 root root 4096 May 29 14:43 ..
  ---------- 1 root root    0 May 29 14:43
  qdhcp-474bd6da-e74f-436a-8408-e10fe5925220

  So, the namespace does exist, but the kernel does not seem to
  recognize it.

  Note that neutron-dhcp is running in a docker container. Also, reboot
  is a `docker restart`

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1460681/+subscriptions