Trove API accepts negative volume size in instance create
Bug #1432212 reported by
Shayne Burgess
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Low
|
Shayne Burgess |
Bug Description
The trove client validates that the volume size specified is 0 or great but the API doesn't. If you issue this request directly against the the API you can try to create an instance with a negative volume this actually fails when the task manager calls the cinder client to create the volume.
A minor issue but it's a bad experience because it always leaves an instance in error state and it really messes with Horizon which has a lot of trouble rending the negative volume size value.
We found this in our pen testing of the API.
Changed in trove: | |
milestone: | none → kilo-rc1 |
Changed in trove: | |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | kilo-rc1 → 2015.1.0 |
To post a comment you must log in.
Same issue exists in cluster create