yahoo-eng-team team mailing list archive

[Brent Eagles <beagles@xxxxxxxxxx>]

Public bug reported:

There may be a race condition involving dnsmasq startup and port
operations. What appears to happen is that dnsmasq is started but the
pid file isn't available when a port change occurs. The dhcp agent then
attempts to start a new dnsmasq instance even though the previous one is
the process of being loaded. Tricky to reproduce manually but does seem
to occur in tempest tests.

Note: this is currently being observed in TripleO ML2/OVS tests. As
dnsmasq is run in a container with a well-defined-name so when the
second container launch fails to because of a naming collision.

** Affects: neutron
     Importance: Undecided
         Status: New

** Summary changed:

- dhcp agent dnsmasq race condition
+ dhcp agent dnsmasq process mgmt race condition between launch and operations

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

Title:
  dhcp agent dnsmasq process mgmt race condition between launch and
  operations

Status in neutron:
  New

Bug description:
  There may be a race condition involving dnsmasq startup and port
  operations. What appears to happen is that dnsmasq is started but the
  pid file isn't available when a port change occurs. The dhcp agent
  then attempts to start a new dnsmasq instance even though the previous
  one is the process of being loaded. Tricky to reproduce manually but
  does seem to occur in tempest tests.

  Note: this is currently being observed in TripleO ML2/OVS tests. As
  dnsmasq is run in a container with a well-defined-name so when the
  second container launch fails to because of a naming collision.

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