Comment 6 for bug 1563029

I have seen bugs like this before. The exception happens in the API (nova-api.log) and is not properly reported to the client. Please attach nova-api.log logs.

The bugs I've seen involve flavor lookups failing (we just fixed a problem related to the nova-api db not migrating the flavors properly which is in the review queue as a 1 liner). I have seen a similar exception where the image id could not be found from glance, resulting in an API exception error. Finally I have seen an error where the networks could not be allocated.

I fixed the first two problems by building centos source instead of centos binary. I think in this case the client locked up during a nova boot operation waiting on flavor access or image access. I'd really look for that 1 liner that fixes the flavor migration into the nova-api database.

Also are you using centos or ubuntu and binary or source?

Thanks
-steve