maas-devel team mailing list archive

["Francis J. Lacoste" <francis.lacoste@xxxxxxxxxxxxx>]

On 12-04-26 09:49 AM, Michael Hughes wrote:
> I'm succeeding to the point of deploying mysql and it went fine (no
> errors,) but MAAS refuses to acknowledge my second node (NODE2-DD27)
> is running:
> 
> $ juju status
> 2012-04-26 08:40:24,362 INFO Connecting to environment...
> 2012-04-26 08:40:25,672 INFO Connected to environment.
> machines:
>   0:
>     agent-state: running
>     dns-name: NODE1-86F0
>     instance-id: /MAAS/api/1.0/nodes/node-c5500a72-f0dd-11e1-91d8-088e02002735/
>     instance-state: unknown
>   1:
>     agent-state: not-started
>     dns-name: NODE2-DD27
>     instance-id: /MAAS/api/1.0/nodes/node-dee7c086-8edf-1271-bb60-0802f01e0035/
>     instance-state: unknown


Hi Michael,

What does the MAAS UI says. Is NODE2-DD27 marked as Allocated or still
ready?

If it's 'Allocated', it probably means that Juju has trouble connecting
to nodes using the DNS name. Does NODE2-DD27 resolve on the bootstrap
node. You should be able to ssh in the bootstrap node by using `juju ssh 0`

Make sure NODE2-DD27 resolves and is reachable from there.

juju debug-log might also give you a better idea of what is the problem.

Cheers



-- 
Francis J. Lacoste
francis.lacoste@xxxxxxxxxxxxx

Attachment: signature.asc
Description: OpenPGP digital signature