This post to the ML seems related / hitting the same
issue:http://lists.openstack.org/pipermail/openstack-
discuss/2021-October/025292.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940976
@johnsom thanks a bunch for getting back to me.
NO I am not using a coordinator. As discussed on IRC, Designate
apparently requires a DLM even when running just as a single instance to
coordinate multiple updates to a single zone?
As I wrote in
Yes, that is what I am asking about.
The configuration setting:
[coordination]
backend_url =
Such that the threads are using the distributed lock manager.
You can also look for this warning message:
@johnsom Could you elaborate what I should check for exactly. I tested
this while having reduced our set of three designate instances to just
one to rule out any side-effects in this regard.
Are you talking about setting up a coordinator as described here?
Did you have the distributed locking service enabled, even for the
single process deployment?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940976
Title:
Race condition in zone serial generation
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940976
Title:
Race condition in zone serial generation on concurrent
** Also affects: designate (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940976
Title:
Race condition in zone serial generation on concurrent
