designate/designate/central
Arjun Baindur 7c2a3be3e4 Make update_status use synchronized_zone
There is a race condition when adding a new recordset to a zone
and when central is processing the update_status from a previous
recordset/zone operation. In the subsequent recordset operation,
central fails to update the zone's action/status in DB to UPDATE/PENDING.
It remains as NONE/ACTIVE, and worker error's out.

Each operation retrieves a different copy in memory of the Zone object
(when it calls self.storage.get_zone). As a result this does not update
the obj_changes field for the zone object for the latter operation.
Therefore the DB update doesn't update any values.

update_status should be synchronized as it updates zone DB

Change-Id: Ib4e0bc567ba8eb54c61c3921d165521bf2f12206
Closes-Bug: #1713875
(cherry picked from commit 12cd654b14)
2018-09-23 10:52:54 +00:00
..
__init__.py Auto-generate designate.conf.sample via genconfig testenv 2017-07-01 21:32:16 +07:00
rpcapi.py Move RPC topics which hard-coded in Designate project. 2017-04-26 19:11:31 +00:00
service.py Make update_status use synchronized_zone 2018-09-23 10:52:54 +00:00