[juju go + hpcloud] juju deploy, just borked?
ian.booth at canonical.com
Mon Mar 25 23:15:45 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
Since the bootstrap node appears to be running ok, it may be better to see
what's happening on the mysql node. The log files of interest would be something
like (after ssh'ing to the machine using juju ssh 1):
On 26/03/13 09:09, David Cheney wrote:
> You can use juju ssh 0 to access the bootstrap node, from then check out
> /var/log/juju/machine-0.log (from memory), it'll explain what has gone wrong.
> On 26/03/13 07:50, Zygmunt Krynicki wrote:
> How long are deployments supposed to take:
> zyga at g580:~$ juju status
> agent-version: 1.9.12
> dns-name: 18.104.22.168
> instance-id: "1023929"
> instance-id: pending
> charm: cs:precise/ubuntu-0
> exposed: false
> machine: "1"
> status: pending
> I ran `juju deploy cs:precise/ubuntu` about 10 minutes ago. Subsequent
> `juju status` calls just show it as pending.
> Looking at https://console.hpcloud.com/compute/az-1_region-a_geo-1/servers
> I see that I have one machine, the bootstrap node.
> If juju were to deploy the ubuntu charm I should see at least two
> machines, correct? If it was going to work, it should probably be
> running by now.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the Juju