"RecordSet not found" while trying to update NS Pool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
New
|
Undecided
|
Tim Simmons |
Bug Description
Version: stable/liberty
Steps to reproduce:
1) Get an actual NS pool list (to acquire its ID)
$ http http://
HTTP/1.1 200 OK
Connection: keep-alive
Content-Length: 504
Content-Type: application/json; charset=UTF-8
Date: Sun, 15 Nov 2015 08:45:44 GMT
X-Openstack-
{
"links": {
"self": "http://
},
"pools": [
{
"id": "794ccc2c-
},
"name": "default",
{
},
{
}
],
}
]
}
2) Try to update this NS pool
$ http --json PATCH http://
HTTP/1.1 404 NOT FOUND
Connection: keep-alive
Content-Length: 141
Content-Type: application/json
Date: Sun, 15 Nov 2015 08:45:57 GMT
X-Openstack-
{
"code": 404,
"message": "Could not find RecordSet",
"request_id": "req-ac23b1e0-
"type": "recordset_
}
3) If there are another NS records in zone(s) present - still fails, but after manual deletion of all non-managed NS records - request above is succeeded.
description: | updated |
Changed in designate: | |
assignee: | nobody → megha (tmegha247) |
assignee: | megha (tmegha247) → nobody |
assignee: | nobody → megha (tmegha247) |
Changed in designate: | |
assignee: | megha (tmegha247) → Tim Simmons (timsim) |
I thought this might be a dup of https:/ /bugs.launchpad .net/designate/ +bug/1500798, looks like it's a bit different, needs more investigation.