yahoo-eng-team team mailing list archive

[Jakub Libosvar <libosvar@xxxxxxxxxx>]

Public bug reported:

There is an infinite loop in OVS agent driven by one variable. If OVG
agent receives SIGTERM signal and loop is running, OVS agent must wait
until execution reaches loop control variable. If at the same time
neutron-server is down, agent still uses rpc call() methods and waits
for response from neutron-server. Several timeouts on rpc must occur
until OVS agents quits. If this whole process of exiting takes more than
90 seconds, systemd by default sends SIGKILL to ovs-agent process which
means ovs-agent didn't exit with exit code 0. RPC calls are not
necessary if we know agent is going to shutdown.

** Affects: neutron
     Importance: Undecided
     Assignee: Jakub Libosvar (libosvar)
         Status: Confirmed

** Changed in: neutron
       Status: New => Confirmed

** Changed in: neutron
     Assignee: (unassigned) => Jakub Libosvar (libosvar)

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

Title:
  OVS agent hangs on rpc calls if neutron-server is down and ovs-agent
  received SIGTERM

Status in OpenStack Neutron (virtual network service):
  Confirmed

Bug description:
  There is an infinite loop in OVS agent driven by one variable. If OVG
  agent receives SIGTERM signal and loop is running, OVS agent must wait
  until execution reaches loop control variable. If at the same time
  neutron-server is down, agent still uses rpc call() methods and waits
  for response from neutron-server. Several timeouts on rpc must occur
  until OVS agents quits. If this whole process of exiting takes more
  than 90 seconds, systemd by default sends SIGKILL to ovs-agent process
  which means ovs-agent didn't exit with exit code 0. RPC calls are not
  necessary if we know agent is going to shutdown.

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