D'Oh of course after the messy trace post i find my typo
I'd accidentally defined glance_api_servers to be IP rather than IP:PORT
while refactoring my configuration management (I'd suspected it was in
there but had been looking in all the wrong places)
-Jon
__
I'd though this was happening before it got to a compute host since no host
was listed in the instances table of the database, but I did manage to hunt
down the RPC exception that happens on the compute node:
2013-08-13 12:12:09.055 AUDIT nova.compute.manager
[req-3ec8ea52-2ef7-4a38-8ccf-4d629a2a1
On 08/12/2013 09:09 AM, Jonathan Proulx wrote:
>
> This is particularly odd since glance was working fine yesterday and to
> my knowlege the only thing I did was turn on more compute nodes...
>
>
> Now when I try and launch an instance it goes almost immediately to
> error state with the fault:
This is particularly odd since glance was working fine yesterday and to my
knowlege the only thing I did was turn on more compute nodes...
Now when I try and launch an instance it goes almost immediately to error
state with the fault:
{u'message': u'ImageNotFound', u'code': 404, u'details': u'Im
