v1 API always gives null for record descriptions, despite v2 recordset having a description?

Bug #1609576 reported by Alexander Monk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Designate
Invalid
Undecided
Unassigned

Bug Description

For example:
krenair@silver:~$ curl -H "Content-Type: application/json" -H "x-auth-token: redacted" -H "x-auth-sudo-project-id: wmflabsdotorg" http://labservices1001.wikimedia.org:9001/v1/domains/933a78c2-3d8d-4ee1-bbef-9ab30be5f972/records/28c927b6-8a9c-45bf-b9a5-afe7f65bb611
{
  "created_at": "2016-08-02T21:02:13.000000",
  "data": "instance-mathosphere.math.wmflabs.org.",
  "description": null,
  "domain_id": "933a78c2-3d8d-4ee1-bbef-9ab30be5f972",
  "id": "28c927b6-8a9c-45bf-b9a5-afe7f65bb611",
  "name": "185.128-25.155.80.208.in-addr.arpa.",
  "priority": null,
  "ttl": null,
  "type": "PTR",
  "updated_at": "2016-08-02T21:21:20.000000"
}
krenair@silver:~$ curl -H "Content-Type: application/json" -H "x-auth-token: redacted" -H "x-auth-sudo-project-id: wmfabsdotorg" http://labservices1001.wikimedia.org:9001/v2/zones/933a78c2-3d8d-4ee1-bbef-9ab30be5f972/recordsets/c458d857-fcff-40d5-97a2-b46c5121fe17
{"status": "ACTIVE", "description": "MANAGED BY dns-floating-ip-updater.py IN PUPPET - DO NOT UPDATE OR DELETE", "links": {"self": "http://labservices1001.wikimedia.org:9001/v2/zones/933a78c2-3d8d-4ee1-bbef-9ab30be5f972/recordsets/c458d857-fcff-40d5-97a2-b46c5121fe17"}, "created_at": "2016-08-02T21:02:13.000000", "updated_at": null, "records": ["instance-mathosphere.math.wmflabs.org.", "beta.math.wmflabs.org."], "zone_id": "933a78c2-3d8d-4ee1-bbef-9ab30be5f972", "version": 1, "ttl": null, "action": "NONE", "type": "PTR", "id": "c458d857-fcff-40d5-97a2-b46c5121fe17", "name": "185.128-25.155.80.208.in-addr.arpa."}

I noticed this issue because I tried to edit a record in Horizon (which uses the v1 API via python-designateclient)... It didn't show any description, but I knew that I had created it with one.
Interestingly the v2 API gives a null updated_at whereas the v1 one does not. Maybe this is because of recordsets vs. records? I did notice the IDs were different... I think I'd still expect every record be created with the description of the recordset. Hmm.

Revision history for this message
Graham Hayes (grahamhayes) wrote :

So, records and recordsets are 2 distinct resources.

When we changed to v2, records became a sub resource of recordsets, and we did some things in the v1 API to allow it to continue working.

However, the descriptions for recordsets cannot be shown on records, as they can have their own description, which is unfortunately hidden in the v2 API.

Changed in designate:
status: New → Invalid
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.