Delayed deletion of records

Bug #1555063 reported by kenichiro matsuda
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Designate
Fix Released
Medium
Unassigned

Bug Description

I use kilo version designate.

I delete a record with the api (Delete a record),
but sometimes deleted record exists in the api (List Records in a Domain) result.
In the re-check a little later, it did not exist in deleted records.

The reason for deletion delay has occurred, I think that it is in the execution method of update_status() of the designate-central.
By "cast ()" The following methods are used, update_status () has become an asynchronous execution.

  PoolManagerAPI.update_domain()
  MdnsAPI.poll_for_serial_number()
  PoolManagerAPI.update_status()
  CentralAPI.update_status()

In the above methods, why use "cast()"?

Tim Simmons (timsim)
Changed in designate:
status: New → Triaged
importance: Undecided → High
milestone: none → mitaka-rc1
no longer affects: designate (Ubuntu)
Changed in designate:
importance: High → Medium
Changed in designate:
status: Triaged → Won't Fix
status: Won't Fix → Fix Released
no longer affects: designate/kilo
no longer affects: designate/liberty
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.