500 on listing zones/recordsets with limit=MAX
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
High
|
Federico Ceratto |
Bug Description
Listing zones/recordsets allows using limit=max per http://
Problem:
If any of the letters in "max" are uppercased, Designate will 500.
To reproduce, make any of the following calls:
GET /v2/zones?limit=MAX
GET /v2/zones?limit=Max
GET /v2/zones?limit=maX
...
GET /v2/zones/
GET /v2/zones/
GET /v2/zones/
...
All of the above requests will return a 500 response with the body,
{
"code": 500,
"type": "unknown",
"request_id": "req-5ececba3-
}
Changed in designate: | |
milestone: | none → liberty-rc1 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in designate: | |
assignee: | nobody → sonu (sonu-bhumca11) |
Changed in designate: | |
status: | Fix Committed → Fix Released |
Changed in designate: | |
milestone: | liberty-rc1 → 1.0.0 |
Fix proposed to branch: master /review. openstack. org/226248
Review: https:/