I hit the same problem, and don't use LXC at all on my setup. I therefore will change this bug to point back to juju-core.
My MaaS lives in a KVM machine on my laptop. It can PXE boot/start-stop other KVM machines living on the same NAT'ed network. - "juju bootstrap --upload-tools" works (the node is spun up, and after the ubuntu install, "juju status" works). - I can "juju deploy" any charm, however: - The machines come up (the node boots, ubuntu gets installed), but "juju status" reports "pending" forever. The machine that is brought up has the same symptoms as reported above: The machine log in /var/log/juju show: 2013-11-05 18:39:02 ERROR juju runner.go:211 worker: exited "deployer": exec ["start" "--system" "jujud-unit-rabbitmq-server-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) Running this command by hand works when run without "--system". Once ran, /var/log/juju contains a unit log as: http://pastebin.ubuntu.com/6371502/ The cloud-init log and cloud-init-output log are: http://pastebin.ubuntu.com/6371297/ http://pastebin.ubuntu.com/6371310/ I further tried to fix the situation manually by symlinking "/var/lib/juju/tools/1.16.2.1-saucy-amd64/" to "/var/lib/juju/tools /unit-mysql-0", but to no avail. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1248283 Title: Juju deploy of Charm in MAAS fails because dbus fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1248283/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
