Comment 15 for bug 1525280

Looking at the logs (for machine1 and the containers), there's a tonne of rsyslog certificate errors. I think these are orthogonal to the issue at hand, but the logs are full of spam because of it.

2015-12-19 00:29:59 INFO juju.worker runner.go:275 stopped "rsyslog", err: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment \"rsyslog\"")
2015-12-19 00:29:59 DEBUG juju.worker runner.go:203 "rsyslog" done: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment \"rsyslog\"")
2015-12-19 00:29:59 ERROR juju.worker runner.go:223 exited "rsyslog": x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "juju-generated CA for environment \"rsyslog\"")
2015-12-19 00:29:59 INFO juju.worker runner.go:261 restarting "rsyslog" in 3s

The fact that juju status shows agent state is pending tends to indicate the agent hasn't started and phoned home, yet cloud init output shows everything ok here:

Starting Juju machine agent (jujud-machine-1-lxc-1)
+ cat
+ start jujud-machine-1-lxc-1
jujud-machine-1-lxc-1 start/running, process 841
+ rm /var/lib/juju/tools/1.25.2-trusty-amd64/tools.tar.gz
+ rm /var/lib/juju/tools/1.25.2-trusty-amd64/juju1.25.2-trusty-amd64.sha256
+ ifconfig
eth1 Link encap:Ethernet HWaddr 00:16:3e:f9:04:6a
          inet addr:10.0.30.13 Bcast:255.255.255.255 Mask:255.255.255.255
          inet6 addr: fe80::216:3eff:fef9:46a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:2207 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1099 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:18937819 (18.9 MB) TX bytes:73447 (73.4 KB)

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1
          RX packets:136 errors:0 dropped:0 overruns:0 frame:0
          TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10528 (10.5 KB) TX bytes:10528 (10.5 KB)

So perhaps there is a connectivity issue between lxc and state server such that the phone home is not received and the rsyslog errors are a symptom of that. Not sure.