juju-core

  1. Bug #1450191
  2. Comment #4

Comment 4 for bug 1450191

Revision history for this message
Ian Booth (wallyworld) wrote : Re: quickstart cannot talk juju on maas 1.7

I don't know much about quickstart, but here's my thoughts....

Juju reports the known node addresses as:

2015-04-29 20:40:59 INFO juju.worker.certupdater certupdater.go:127 State Server cerificate addresses updated to ["public:maas-node-214.maas" "local-cloud:10.0.40.156"]
I don't think this is a Juju issue - it appears DNS related.

quickstart is attempting to connect to the MAAS node on it's cloud internal (private) address, not the public address which is a DNS name.

ie units and other things can connect to wss://maas-node-214.maas:17070/environment/bcef503c-45ef-42f3-804f-7e6b34040cba/api

quickstart is attempting to connect to wss://10.0.40.156:443/ws/environment/bcef503c-45ef-42f3-804f-7e6b34040cba/api

The quickstart logs show:

20:41:16 WARNING watchers:106 cannot resolve public maas-node-214.maas address, looking for another candidate: [Errno -2] Name or service not known
unit placed on 10.0.40.156

It appears quickstart can't resolve the DNS name, so instead chooses the private IP address.