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

Nicolas Bock 1871332 at bugs.launchpad.net
Fri Apr 9 21:16:46 UTC 2021


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.

** Description changed:

+ [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.

-- 
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:
  New
Status in Ubuntu Cloud Archive stein series:
  New
Status in Designate:
  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



More information about the Ubuntu-openstack-bugs mailing list