[Bug 1871332] Re: Many records created at the same time may lead to a race condition

[Corey Bryant]

This bug was fixed in the package designate - 1:8.0.1-0ubuntu1~cloud1
---------------

 designate (1:8.0.1-0ubuntu1~cloud1) bionic-stein; urgency=medium
 .
   [ Chris MacNaughton ]
   * d/control: Update VCS paths for move to lp:~ubuntu-openstack-dev.
 .
   [ Nicolas Bock ]
   * d/p/0001-Adding-distributed-locking-to-central.patch: Fix race with
     multiple instances of designate-central (LP: #1871332).


** Changed in: cloud-archive/stein
       Status: Fix Committed => Fix Released

** Changed in: cloud-archive/train
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1871332

Title:
  Many records created at the same time may lead to a race condition

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in Designate:
  Fix Released
Status in designate package in Ubuntu:
  Fix Released
Status in designate source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * When multiple records are created at the very same time the
     serial number may not be updated properly. This is especially
     easy to reproduce with the designate-sink and creating 2+ VMs
     at the same time.

   * The fix is included in the upstream Stein branch but is not
     included in any Stein release.

  [Test Plan]

   * Create multiple DNS recordsets in parallel and verify that
     they are all included in the DNS zone on the backend DNS
     server. It is important to created those recordsets very close
     in time so that the bug is triggered. Using a deployment
     mechanism such as Terraform might help.

  [Where problems could occur]

   * The upstream fix introduces a central lock which prevents the
     bug but also leads to performance degradation because this
     lock functions as a parallel barrier.

  [Original description]

  When multiple records are created at the very same time the serial
  number may not be updated properly. This is especially easy to
  reproduce with the designate-sink and creating 2+ VMs at the same
  time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1871332/+subscriptions