I'm repeatedly deploying a stack with 8 machines and around 50% of the time (small sample) one unit remains pending indefinitely:
$ juju status sca-dp-fe
environment: local
machines:
"5":
agent-state: pending
instance-id: michael-local-machine-5
series: trusty
hardware: arch=amd64
services:
sca-dp-fe:
charm: local:trusty/apache2-0
exposed: false
units:
sca-dp-fe/0:
agent-state: allocating
machine: "5"
I had been thinking I was running out of space, but checked and lxc reports the container as started. Checking the machine log for that machine shows that the machine is unable to connect to the api server due to the juju-generated CA being rejected, while all other machines obviously don't have this problem:
http://paste.ubuntu.com/11071952/
$ apt-cache policy juju-core
juju-core:
Installed: 1.23.2-0ubuntu1~14.04.1~juju1
Candidate: 1.23.2-0ubuntu1~14.04.1~juju1
Destroying the environment (needing --force) and rebootstraping is currently the only way I know to get around this :/
Are you using a script to deploy? If so, please include a copy of the script.