canonical-ci-engineering team mailing list archive

[Evan Dandrea <evan.dandrea@xxxxxxxxxxxxx>]

On 18 September 2013 23:22, Andy Doan <andy.doan@xxxxxxxxxxxxx> wrote:
> this works (tangent question: how do i get this to use an m1.medium?).

--constraints "mem=3840" should do it.

> This *seems* to work - I see a new process running on my instance like:
>
>  python2 -c import sys; skip_imports=1; verbosity=0; exec
> compile(sys.stdin.read(764), "assembler.py", "exec")

What is this process? From the "error details" below, you appear to be
correctly running gojuju and not pyjuju, so I'm assuming it's not the
latter.

> Then I run "juju status" and get:
>
> $ juju status -e openstack
> error: Unable to connect to environment "openstack".
> Please check your credentials or use 'juju bootstrap' to create a new
> environment.
>
> Error details:
> cannot log in to admin database

Is there anything of note in /var/log/juju on the bootstrap node?

Happy to walk through this with you on IRC if you're still having issues.