It seems like this is a bug in python-novaclient. I believe the recent
change to enforce that flavor ids are either int-like or uuid-like may have
been made in error. At minimum, I believe it is backwards-incompatible,
despite being part of a minor point release (changed from 2.13 to 2.14).
See
Hi,
Referring to https://bugs.launchpad.net/nova/+bug/1202136, it seems that the
novaclient
validates the flavor ID to be either an integer or a UUID string. This check
does not exist in Nova, so currently strings
are also accepted as flavor IDs by Nova when direct restful API calls are made.
