juju machine 0 watcher unable to connect to units

[Edward Hope-Morley]

I have performed a fresh deployment using Juju 1.25.0-0ubuntu1~14.04.1~juju1 and I observed that the deployment proceeds successfully i.e. units are deployed and their local logs display no errors yet the bootstrap node all-machines.log (and therefore 'juju debug-log') is devoid of the unit juju logs and apparently the bootstrap node watchers are unable to discover unit public-addresses and connect to them (See attached all-machines.log).

This is using MAAS (1.8.3+bzr4053-0ubuntu1~trusty1) and I have 5 managed networks defined in MAAS.

[Ryan Beisner (1chb1n)]

FTR, 1.25.3 from proposed gives:

ubuntu@beisner-bastion:~/bzr/openstack-charm-testing$ juju debug-log
ERROR cannot open log file: open /var/log/juju/all-machines.log: no such file or directory

# node 0:
ubuntu@juju-beis0:~$ ll /var/log/juju
total 52
drwxr-xr-x 2 syslog adm 4096 Jan 25 21:20 ./
drwxrwxr-x 9 root syslog 4096 Jan 25 21:20 ../
-rw------- 1 syslog syslog 44654 Jan 25 21:49 machine-0.log