Juju 2.0 Trunk launches disconnected nodes

[Tom Barber]

I have no idea how to reproduce this. Its Juju Trunk LXD compat branch and LXD 2.0 alpha 4.

Happened twice today. This time doing:

juju add-unit pdi

at which point a new container is started and juju tells me everything is installed and running, but the container itself hasn't even installed the charm in /var/lib/juju/agents.....

http://ibin.co/2YlapnApEXm7

As you can see on the screenshot, pdi/2 is considered to be running, but its ip address is 127.0.0.1

If I look at where it would have been installed on the host, its not their either. So somehow, somewhere Juju is running through the installation hooks and passing them, but seemingly nowhere I can see.

The only logs available are: http://paste.ubuntu.com/15260117/

[Tom Barber (spicule)]

So I decided to destroy my controller and sync up and start-afresh. This time my controller is on 127.0.0.1 which breaks the init of the first charm... something fishy going on inside LXD I think.

[Tom Barber (spicule)]

After a reboot, my controller is back to an IP, my first node is also assigned an ip, add-unit once again sets the IP address to 127.0.0.1 even though LXC has given it a 10.0.3. ip address

[John A Meinel (jameinel)]

From the duplicate bug #1552423
I also noticed Juju is trying to connect to localhost during bootstrap, which seems to me like it'd never be the right thing to do:

Bootstrapping model "lxd" [156/953]
Starting new instance for initial controller
Launching instance
 - juju-bbeb3f29-cca8-4d8a-8ceb-c13ad3ead94e-machine-0
Building tools to upload (2.0-beta2.1-trusty-amd64)
Installing Juju agent on bootstrap instance
Waiting for address
Attempting to connect to 10.0.3.68:22
Attempting to connect to fe80::216:3eff:fe5f:f34e:22
Attempting to connect to 127.0.0.1:22
Attempting to connect to ::1:22

I wonder if this is carry over from when we had "local" provider. Or if it is just that we added filtering for all the other providers to remove "local only" addresses, and when LXD was implemented it didn't do that step.

[Tom Barber (spicule)]

Another quirk I noticed John, was, if I do juju deploy realtime-syslog-analytics all those nodes in the bundle get valid IP's. So, weirdly bundle deployment works fine, but single charm deployment is broken(but sometimes not)

[John A Meinel (jameinel)]

Patch: https://github.com/juju/juju/pull/4636

[Tom Barber (spicule)]

Patch works well!