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
)
This commit is contained in:
parent
5c1c636c29
commit
af1bb8a36a
|
@ -2302,6 +2302,7 @@ class Service(service.RPCService, service.Service):
|
|||
@notification('dns.domain.update')
|
||||
@notification('dns.zone.update')
|
||||
@transaction
|
||||
@synchronized_zone()
|
||||
def update_status(self, context, zone_id, status, serial):
|
||||
"""
|
||||
:param context: Security context information.
|
||||
|
|
Loading…
Reference in New Issue