The 'next' link not shown
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Confirmed
|
Undecided
|
sonu |
Bug Description
Reproduce steps:
1. openstack zone create show.bug.com. --email <email address hidden>
2. openstack recordset create 90783c85-
3. openstack recordset create 90783c85-
The following filtering request shows there are 2 matched rrsets, but only one shown up and the 'next' link is missing.
curl -H "x-auth-token: <T>" "http://
{
"metadata": {
"total_count": 2
},
"links": {
"self": "http://
},
"recordsets": [
{
"name": "email-
"id": "91c0b00b-
"type": "A",
"project_id": "92937889c00c4a
"zone_name": "show.bug.com.",
"action": "CREATE",
"ttl": null,
"status": "PENDING",
"
"links": {
"self": "http://
},
"created_at": "2016-07-
"updated_at": null,
"records": [
"10.0.0.2",
"10.0.0.1"
],
"zone_id": "90783c85-
"version": 1
}
]
}
Changed in designate: | |
importance: | Undecided → Critical |
status: | New → Triaged |
milestone: | none → rc1 |
Changed in designate: | |
assignee: | nobody → sonu (sonu-bhumca11) |
The fix should be tested to make sure it won't impact the performance of recordsets API (i.e. /v2/recordsets) under a large-scale dataset.