A fim de adicionar mais informações sobre este assunto: Eu também estou obtendo o mesmo comportamento ao implantar o charme "juju-gui" em um nó MAAS baseado no Saucy Salamander.
Eu também tenho esse charme através do bzr (com o charme, pegue juju-gui).
Estou observando que temos o mesmo problema com diferentes charms, séries do Ubuntu e até mesmo a versão do Juju.
Meu status de juju:
services:
juju-gui:
charm: local:saucy/juju-gui-99
exposed: false
units:
juju-gui/0:
agent-state: pending
machine: "1"
public-address: node2.opc-ss.com
Faz o login no nó:
2013-11-19 08:51:08 INFO juju.worker.deployer deployer.go:146 deploying unit "juju-gui/0"
2013-11-19 08:51:08 INFO juju.worker.upgrader upgrader.go:134 desired tool version: 1.16.3
2013-11-19 08:51:08 INFO juju.worker.machiner machiner.go:52 "machine-1" started
2013-11-19 08:51:09 WARNING juju.worker.deployer simple.go:244 installer: cannot remove "/var/lib/juju/agents/unit-juju-gui-0": remove /var/lib/juju/agents/unit-juju-gui-0: directory not empty
2013-11-19 08:51:09 ERROR juju runner.go:211 worker: exited "deployer": exec ["start" "--system" "jujud-unit-juju-gui-0"]: exit status 1 (start: Unable to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
2013-11-19 08:51:09 INFO juju runner.go:245 worker: restarting "deployer" in 3s
2013-11-19 08:51:09 INFO juju.provisioner provisioner_task.go:102 Starting up provisioner task machine-1
2013-11-19 08:51:12 INFO juju runner.go:253 worker: start "deployer"
2013-11-19 08:51:12 INFO juju.worker.deployer deployer.go:106 checking unit "juju-gui/0"
2013-11-19 08:51:12 INFO juju.worker.deployer deployer.go:106 checking unit "juju-gui/0"