errors when using flavors with uuid

[Andrey Shestakov]

{"badRequest": {"message": "Validation error: instance['flavorRef'] u'7b67e99a-4289-48d7-819f-e55875343e05' is not valid under any of the given schemas; u'7b67e99a-4289-48d7-819f-e55875343e05' does not match 'http[s]?://(?:[a-zA-Z]|[0-9]|[$-_@.&+]|[!*\\\\(\\\\),]|(?:%[0-9a-fA-F][0-9a-fA-F]))+'; u'7b67e99a-4289-48d7-819f-e55875343e05' is too long; u'7b67e99a-4289-48d7-819f-e55875343e05' is not of type 'integer'", "code": 400}}

on flavor list:

2013-09-16 16:33:14.262 31148 ERROR trove.common.wsgi [req-e9637cd3-8adb-411d-83d7-3f7e4b2b2030 admin 3a551aeae0d64605a7492ebb5df19f0c] 38a14c08-74cf-421a-b104-6c01b4523abc: invalid literal for int() with base 10: '7b67e99a-4289-48d7-819f-e55875343e05'

[Justin Hopper (justin-hopper)]

Andrey -

Is our api supposed to support just a UUID...without the full reference? If so, then we just need to add plain UUID format as an option for the flavor_ref. It currently looks like it supports "integer" and "http://host:port/UUID"

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/48735

[Michael Yu (michayu-c)]

Hi,

I recently joined the Trove community.

I'm still ramping up on the code and wanted to see if I can help out with any Medium and lower priority bugs. Thus, I was looking into this one.

Was Justin's question (see above) answered? Is our api suppose to support just a UUID without the full reference?

Thanks,
Michael Yu

[rathin049 (rathin049)]

Hi,
I am trying to setup trove on the openstack env, and I am running into the same error. Please could you give a workaround for this? Or is this fix available? If so, how to apply the fix in my current environement?

Thanks
rathin