Creating a configuration with a large parameter value causes HTTP 422
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Medium
|
Duk Loi |
Bug Description
MySQL has a variable called myisam_
Steps to Reproduce
1. Make a call to <api>/datastore
This returns the parameter details of myisam_
{"max": 184467440737095
2. Attempt to create a configuration with myisam_
<api>/configura
HTTP 422 Unprocessable Entity
{"unprocessable
3. I suspect the value is being limited by python's max_int value (92233720368547
----
9223372036854775808 does not work:
<api>/configura
HTTP 422 Unprocessable Entity
{"unprocessable
----
9223372036854775807 does work:
<api>/configura
HTTP 200 OK
{"configuration": {"description": null, "values": {"myisam_
----
A GET on this configuration works:
<api>/configura
HTTP 200 OK
{"configuration": {"description": null, "values": {"myisam_
Changed in trove: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in trove: | |
assignee: | nobody → Duk Loi (duktesora) |
Changed in trove: | |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | kilo-1 → 2015.1.0 |
Retained importance to "Medium" (bugscrub, 2014-10-23)