Designate record deletion using wrong event name
Bug #1550506 reported by
Steve McLellan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Searchlight |
Fix Released
|
High
|
Lakshmi N Sampath |
Bug Description
It looks like deletions on designate records issues a 'dns.record.delete' event, not 'dns.recordset.
Changed in searchlight: | |
assignee: | nobody → Neha (neha-m-pande) |
Changed in searchlight: | |
milestone: | none → mitaka-rc1 |
importance: | Undecided → High |
Changed in searchlight: | |
assignee: | nobody → Lakshmi N Sampath (lakshmi-sampath) |
Changed in searchlight: | |
milestone: | mitaka-rc1 → mitaka-rc2 |
Changed in searchlight: | |
status: | New → In Progress |
To post a comment you must log in.
Looking at the designate source (designate/ central/ service. py) there are notifications for dns.recordset and dns.record; we may need to handle both. Need to talk to the designate team.