When Trove moved to support alphanumeric flavor ids, the case of having
a numeric string id with leading zeros was not taken into account.
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.
This behavior has been fixed and unit tests created.
Reviewed: https:/ /review. openstack. org/342457 /git.openstack. org/cgit/ openstack/ trove/commit/ ?id=afb29a398cc 73849ded2ef1915 13346cebb14834
Committed: https:/
Submitter: Jenkins
Branch: master
commit afb29a398cc7384 9ded2ef19151334 6cebb14834
Author: Peter Stachowski <email address hidden>
Date: Thu Jul 14 22:32:05 2016 +0000
Support flavor ids with leading '0'
When Trove moved to support alphanumeric flavor ids, the case of having
a numeric string id with leading zeros was not taken into account.
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.
This behavior has been fixed and unit tests created.
Change-Id: I87a8ac98d4358b 75182c987f584c6 098398a0c2a a6cbfbb1cfc61c4 9fbbf7379af
Depends-On: I5acdec576a2e7d
Closes-Bug: #1603187