yahoo-eng-team team mailing list archive

[Eugene Nikanorov <enikanorov@xxxxxxxxxxxx>]

Public bug reported:

In some cases when L3 agent is restarted, it can't detect that ns-
metadata-proxy process is already running in the qrouter-namespace so L3
agent spawns it again and again with each restart.

After some number of ns-metadata-proxy processes running in a namespace, L3 agent hangs on spawning additional process.
The symptoms are that router processing loop is getting stuck on one of the router, so remaining routers are not processed.

The workaround is to kill ns-metadata-proxy processes from that router's
namespace and restart L3 agent.

** Affects: neutron
     Importance: Low
         Status: Confirmed


** Tags: l3-ipam-dhcp

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

Title:
  L3 agent hangs while processing a router

Status in OpenStack Neutron (virtual network service):
  Confirmed

Bug description:
  In some cases when L3 agent is restarted, it can't detect that ns-
  metadata-proxy process is already running in the qrouter-namespace so
  L3 agent spawns it again and again with each restart.

  After some number of ns-metadata-proxy processes running in a namespace, L3 agent hangs on spawning additional process.
  The symptoms are that router processing loop is getting stuck on one of the router, so remaining routers are not processed.

  The workaround is to kill ns-metadata-proxy processes from that
  router's namespace and restart L3 agent.

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