'ERROR juju.cmd supercommand.go:430 no instances found' when bootstrapping Juju on OpenStack Juno

[Martin Packman]

On 23/04/2015, Robert Day <Robert.Day at metaswitch.com> wrote:
> Martin, Mark,
>
> Thank you! That was indeed the problem - once I'd changed that entry to an
> IP address (and fixed a couple of similar problems with my metadata files
> not being accessible, where the error messages were much easier to diagnose
> from), everything started working, and I've now successfully got my charms
> working on my OpenStack environment.

Great!

I put up a branch last night to make the error handling when listing
instances in the openstack provider saner, so this kind of thing
should be easier to diagnose in future.

Martin