python-novaclient

'imageref' error with Nova API v1.1

Bug #892196 reported by klmitch
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-novaclient
Fix Released
High
Unassigned

Bug Description

Received an imageref error when attempting to build instance.

Replacing imageId with imageRef and flavorId with flavorRef bypassed the problem.

Revision history for this message
klmitch (q-noreply) wrote :

Newest 1.1 spec gets rid of *Refs, look for changes in the next week or two.

Revision history for this message
klmitch (q-noreply) wrote :

also watching this bug--it's impacted me.

Revision history for this message
klmitch (q-noreply) wrote :

Actually, looks like the API will use imageRef and flavorRef after all. So we should be able to update this - presumably we want to maintain backward compatibility with 1.0 though?

Revision history for this message
klmitch (q-noreply) wrote :

Presumably, but last time I looked at the code (just the other day) it looked like it tries to parse the version out of the auth_url. That's a hack IMO--it should get the version from other metadata from the authentication response--but at least it gets us version information that can be used to select the appropriate parameters. It looks like the version goes into the <instance>.client.version attribute, and it consists of the first path component that begins with 'v'.

Revision history for this message
klmitch (q-noreply) wrote :

This will be addressed in the 1.1 version of the client bindings - coming soon.

Thierry Carrez (ttx)
affects: nova → python-novaclient
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.