The API does not return a status field for recordsets
Bug #1409824 reported by
Paul Glass
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
High
|
Vinod Mangalpally |
Bug Description
I see that there is a status field in the records table. From what I can tell, this status field correctly reflects a record's status on the backend nameserver. But there is no way for a user to retrieve that status through the API (for either /v1/records or /v2/recordsets) which means the user never knows when a record(set) change is live on the nameserver.
In fact, the API returns a 201 on a POST /v2/zones/
I'll also point out that a zone's status does not move to pending when record CUD happens (although I'm not claiming that it should necessarily).
Changed in designate: | |
milestone: | none → kilo-2 |
Changed in designate: | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in designate: | |
milestone: | kilo-2 → kilo-3 |
Changed in designate: | |
status: | Fix Committed → Fix Released |
Changed in designate: | |
milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/152174
Review: https:/