The API does not return a status field for recordsets

Bug #1409824 reported by Paul Glass
6
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/{zone_id}/recordsets, which should at least be a 202 to indicate an asynchronous operation.

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
Kiall Mac Innes (kiall)
Changed in designate:
importance: Undecided → High
status: New → Triaged
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to designate (master)

Fix proposed to branch: master
Review: https://review.openstack.org/152174

Changed in designate:
assignee: nobody → Vinod Mangalpally (vinod-mang)
status: Triaged → In Progress
Kiall Mac Innes (kiall)
Changed in designate:
milestone: kilo-2 → kilo-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to designate (master)

Reviewed: https://review.openstack.org/152174
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=1b290830f3d287d9ae8e6adbd81376ceba961722
Submitter: Jenkins
Branch: master

commit 1b290830f3d287d9ae8e6adbd81376ceba961722
Author: Vinod Mangalpally <email address hidden>
Date: Thu Feb 5 12:29:19 2015 -0600

    Return a status field from the recordsets API

    Currently on a get for a recordset, there is no status
    returned. In the database schema, status only exists on
    records.

    The Recordset object now has 2 read only fields - action
    and status. The action and status fields are calculated
    based on the records. The status is the worst of all the
    records in order of ERROR, PENDING, ACTIVE.

    action is set to UPDATE if present. CREATE and
    DELETE are set if they are the only ones. Otherwise
    action is set to NONE

    If there are no records in the recordset the action and
    status would always be 'NONE' and 'ACTIVE'.

    Change-Id: Idca4d30db67e2bb29d08e11b3d22685422a6b5e9
    Closes-Bug: 1409824

Changed in designate:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in designate:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in designate:
milestone: kilo-3 → 2015.1.0
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.