Status not included in recordset notifications

Bug #1602382 reported by Steve McLellan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Designate
Triaged
High
sajuptpm

Bug Description

On creating a recordset (openstack recordset create <zone>) a dns.recordset.create notification is emitted, followed later by a dns.zone.update notification.

The recordset notification contains all information about a recordset except 'status', for some reason. I would expect to see 'status' in the payload and for a dns.recordset.update notification once the status changes (from PENDING->ACTIVE, or to an error state).

Also possibly related, I see 'version: 1' in the notification payload even though the command's going through the V2 endpoint.

Tested on master July 12th 2016.

Tim Simmons (timsim)
Changed in designate:
status: New → Triaged
importance: Undecided → High
milestone: none → newton-3
Changed in designate:
milestone: newton-3 → none
sajuptpm (sajuptpm)
Changed in designate:
assignee: nobody → sajuptpm (sajuptpm)
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.