yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: neutron
       Status: Fix Committed => Fix Released

** Changed in: neutron
    Milestone: None => juno-1

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

Title:
  Record and log reason for dhcp agent resync

Status in OpenStack Neutron (virtual network service):
  Fix Released

Bug description:
  A dhcp resync can be triggered at a number of points, but the actual
  resync is done asynchronously by a helper thread. This means by the
  time the resync happens, it's hard to establish what actually caused
  it.

  I've seen a number of problems in production systems that cause
  excessive resyncs. One is a ipv6/dnsmasq issue (rhbz#1077487) and
  another is db corruption with duplicate entries [1]. The resync
  triggers a whole lot of logs itself, so it becomes very unclear how to
  establish any causality.

  What I propose is to keep track of what triggered the resync with some
  helpful information.

  [1] The logs will contain output like "DBDuplicateEntry
  (IntegrityError) (1062, "Duplicate entry
  '6d799c6a-7a09-4c1e-bb63-7d30fd052c8a-d3e3ac5b-9962-428a-a9f8-6b2' for
  key 'PRIMARY'") ..." in this case

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