Flavor ids with leading '0' not supported in Trove
Bug #1603187 reported by
Peter Stachowski
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Fix Released
|
High
|
Peter Stachowski | ||
Bug Description
When Trove moved to support alphanumeric flavor ids, the case of having a numeric string id with leading zeros was not taken into account. The behavior on the client side is to see if the id is all digits, and if so it is converted to an int. That means that a flavor of '01' will be incorrectly interpreted as '1'. On the server side the code checks if the flavor id can be converted to an int, and if so then sets it as such - the manifestation being that if the str_id is '01' then the id will be set to '1' instead of None as it should be.
The logic should be unified (say to "id.isdigit() and not id.startswith(
| Changed in trove: | |
| assignee: | nobody → Peter Stachowski (peterstac) |
| importance: | Undecided → High |
| milestone: | none → next |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to trove (master) | #1 |
| Changed in trove: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to trove (master) | #2 |
| Changed in trove: | |
| status: | In Progress → Fix Released |
Revision history for this message
| Doug Hellmann (doug-hellmann) wrote Fix included in openstack/trove 6.0.0.0b3 | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote | #4 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/