[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Setting dbus task to Low priority, for triage purposes. I think the primary fix that needs to happen here is in juju. ** Changed in: dbus (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core 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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
@racb I don't see why this is anythign to do with juju. ubuntu@cloud1:~$ sudo status dbus dbus start/running, process 464 ubuntu@cloud1:~$ sudo restart networking 4init: Disconnected from system bus 4init: whoopsie main process ended, respawning networking start/running ubuntu@cloud1:~$ sudo status dbus dbus stop/waiting -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1248283 Title: dbus does not restart when 'restart networking' command is issued. 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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
So quite simply, 1. dbus stops on deconfiguring-networking 2. restart networking issues deconfiguring-networking 3. dbus only starts on local-filesystems, so it never restarts. Somehow dbus needs to be made to restart when networking restarts, or it simply should not shut down at deconfiguring-networking. ** Summary changed: - Juju deploy of Charm in MAAS fails because dbus fails + dbus does not restart when 'restart networking' command is issued. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1248283 Title: dbus does not restart when 'restart networking' command is issued. 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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Setting dbus task to Low priority, for triage purposes. I think the primary fix that needs to happen here is in juju. ** Changed in: dbus (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
So quite simply, 1. dbus stops on deconfiguring-networking 2. restart networking issues deconfiguring-networking 3. dbus only starts on local-filesystems, so it never restarts. Somehow dbus needs to be made to restart when networking restarts, or it simply should not shut down at deconfiguring-networking. ** Summary changed: - Juju deploy of Charm in MAAS fails because dbus fails + dbus does not restart when 'restart networking' command is issued. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248283 Title: dbus does not restart when 'restart networking' command is issued. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1248283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
@racb I don't see why this is anythign to do with juju. ubuntu@cloud1:~$ sudo status dbus dbus start/running, process 464 ubuntu@cloud1:~$ sudo restart networking 4init: Disconnected from system bus 4init: whoopsie main process ended, respawning networking start/running ubuntu@cloud1:~$ sudo status dbus dbus stop/waiting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248283 Title: dbus does not restart when 'restart networking' command is issued. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1248283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dbus (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core 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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
I'm hitting this problem inside Precise KVM nodes. The bottom of cloud- init-output.log has this: + start jujud-machine-3 jujud-machine-3 start/running, process 2244 Traceback (most recent call last): File /usr/lib/python2.7/logging/handlers.py, line 807, in emit self._connect_unixsocket(self.address) File /usr/lib/python2.7/logging/handlers.py, line 745, in _connect_unixsocket self.socket.connect(address) File /usr/lib/python2.7/socket.py, line 224, in meth return getattr(self._sock,name)(*args) error: [Errno 111] Connection refused Logged from file __init__.py, line 116 The MAAS KVM node is on Saucy. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core 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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dbus (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
I'm hitting this problem inside Precise KVM nodes. The bottom of cloud- init-output.log has this: + start jujud-machine-3 jujud-machine-3 start/running, process 2244 Traceback (most recent call last): File /usr/lib/python2.7/logging/handlers.py, line 807, in emit self._connect_unixsocket(self.address) File /usr/lib/python2.7/logging/handlers.py, line 745, in _connect_unixsocket self.socket.connect(address) File /usr/lib/python2.7/socket.py, line 224, in meth return getattr(self._sock,name)(*args) error: [Errno 111] Connection refused Logged from file __init__.py, line 116 The MAAS KVM node is on Saucy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
** Changed in: juju-core Milestone: 1.17.1 = 1.18.0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core 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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
** Changed in: juju-core Milestone: 1.17.1 = 1.18.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
** Tags added: ubuntu-openstack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core 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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
** Changed in: juju-core Milestone: None = 1.17.1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core 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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
** Tags added: ubuntu-openstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
** Changed in: juju-core Milestone: None = 1.17.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Also affects: dbus (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: juju-core (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu Trusty) Status: New = Triaged ** Changed in: juju-core (Ubuntu Trusty) Importance: Undecided = High ** Also affects: dbus (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: juju-core (Ubuntu Saucy) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu Saucy) Status: New = Triaged ** Changed in: juju-core (Ubuntu Saucy) Importance: Undecided = High ** No longer affects: dbus (Ubuntu Saucy) ** No longer affects: dbus (Ubuntu Trusty) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core 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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Also affects: dbus (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: juju-core (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu Trusty) Status: New = Triaged ** Changed in: juju-core (Ubuntu Trusty) Importance: Undecided = High ** Also affects: dbus (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: juju-core (Ubuntu Saucy) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu Saucy) Status: New = Triaged ** Changed in: juju-core (Ubuntu Saucy) Importance: Undecided = High ** No longer affects: dbus (Ubuntu Saucy) ** No longer affects: dbus (Ubuntu Trusty) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
MAAS on its own does not deploy a stopped dbus service in my testing; it only happens when juju is involved. I've isolated this to service networking restart done by juju using cloud-init userdata. I've updated the description. I think a fix for juju would be straightforward: don't do that; use more targeted ifdown and ifup as required instead. Note that the ifdown should be called before changing /etc/network/interfaces. However, adding a dbus task, as it is arguable that dbus should not die in this case, and certainly not silently. A Won't Fix resolution for dbus dying might be acceptable, though, if it is not expected to survive all network interfaces being deconfigured. But a log message explaining would be nice. ** Description changed: + [Impact] + + juju fails to deploy charms on Saucy. + + [Steps to Reproduce] + + On Saucy: + + root@foo:~# dpkg-query -W dbus + dbus 1.6.12-0ubuntu10 + root@foo:~# status dbus + dbus start/running, process 817 + root@foo:~# service networking restart + networking stop/waiting + networking start/running + root@foo:~# status dbus + dbus stop/waiting + + Verified on amd64. I believe this also affects armhf. + + [Analysis] + + Either: + + 1) dbus shouldn't fail when networking is restarted; or + 2) juju should not restart networking in this way as a runcmd in cloud-init userdata, and then expect dbus to work. + + The relevant part of juju's userdata is: + + - cat /etc/network/eth0.config EOF\niface eth0 inet manual\n\nauto br0\niface + br0 inet dhcp\n bridge_ports eth0\nEOF\n + - sed -i s/iface eth0 inet dhcp/source \/etc\/network\/eth0.config/ /etc/network/interfaces + - service networking restart + + I assume juju is restarting networking to set up the bridge that it + configured; in this case, an ifdown eth0 and a subsequent ifups as + required should suffice. No need to restart everything (eg. lo, etc) + which I [rbasak] presume is causing the issue. + + Note that dbus appears to silently fail; if it is going to stop, it + should do so with a sensible log message. + + [Original Description] + I'm running a MAAS and Juju enviornment using 64-bit Ubuntu Server 13.10 for the MAAS node as well as all juju nodes, including the bootstrap node. I can't seem to deploy any charms to the nodes without the services getting stuck in a 'pending' state. The problem seems to be that upon charm deployment dbus for some reason is stopped, and thus the whole process of deploying the charm gets stuck. It is almost verbatim of the problem someone appears to have hit on raring, too: http://askubuntu.com/questions/364714/juju-deploy-of-charm-mysql-in- maas-provider-failing-after-successful-bootstrap For me, however, it's not just mysql...it's any service I try to deploy. juju release: 1.16.2-0ubuntu1~ubuntu13.10.1~juju1 maas version: 1.4+bzr1693+dfsg-0 Ubuntu OS: 13.10, 64-bit for everything Steps to reproduce: 1) Set up a maas server using 13.10 with all the latest updates. 2) Install juju-core from the stable ppa (1.16.2 in this case). 3) Enlist and commission some nodes. 4) download some charms locally (I'm in a semi-restricted network environment, so, it's easier for me to pull down the charms locally). For example, bzr branch lp:charms/rabbitmq-server - 5) bootstrap the juju environment. Due to restrictions in my network I have to use juju bootstrap --upload-tools. Firewall blocks the ability to run juju sync-tools beforehand. + 5) bootstrap the juju environment. Due to restrictions in my network I have to use juju bootstrap --upload-tools. Firewall blocks the ability to run juju sync-tools beforehand. 6) Once the environment is bootstrapped, try to deploy a charm. This is what I used: juju deploy --repository=charms/ local:rabbitmq-server --show-log. Actual results: - Installation of the OS goes fine, along with the cloud-init after reboot. I can also ssh into the node via juju. - The charm, however, stays in a 'pending' state long after it is deployed on the server. - ssh-ing into the node and looking at /var/log/juju/machine-x.log reveals that the deployment stage fails due to being unable to connect to the system bus. - This seems to prevent the charm from ever deploying. + Installation of the OS goes fine, along with the cloud-init after reboot. I can also ssh into the node via juju. + The charm, however, stays in a 'pending' state long after it is deployed on the server. + ssh-ing into the node and looking at /var/log/juju/machine-x.log reveals that the deployment stage fails due to being unable to connect to the system bus. + This seems to prevent the charm from ever deploying. Expected results: - OS installs and charm deploys without issue. + OS installs and charm deploys without issue. Workaround: I can work around this by ssh-ing into the node and starting dbus by hand. I then go back and re-deploy the charm via juju using:
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New = Confirmed -- 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/ubuntu/+source/lxc/+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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Adding juju-core back because the bug still does affect functionality of juju-core and needs to be tracked in juju-core project, regardless of where/how the fix is applied. ** Also affects: lxc Importance: Undecided Status: New ** No longer affects: lxc ** Also affects: juju-core Importance: Undecided Status: New ** Changed in: juju-core Status: New = Confirmed -- 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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Changing back to juju-core since this affects me, and I'm not using LXC containers at all. ** Package changed: lxc (Ubuntu) = juju-core (Ubuntu) ** Tags added: landscape -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core 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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
I can confirm that I experience exactly the same issue using Juju with MAAS and nodes all under KVM. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core 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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
** Changed in: juju-core Status: Confirmed = Triaged ** Changed in: juju-core Importance: Undecided = High ** Package changed: juju-core (Ubuntu) = maas ** Changed in: maas Status: Confirmed = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core 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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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/ubuntu/+source/lxc/+bug/1248283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Adding juju-core back because the bug still does affect functionality of juju-core and needs to be tracked in juju-core project, regardless of where/how the fix is applied. ** Also affects: lxc Importance: Undecided Status: New ** No longer affects: lxc ** Also affects: juju-core Importance: Undecided Status: New ** Changed in: juju-core Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
I can confirm that I experience exactly the same issue using Juju with MAAS and nodes all under KVM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Changing back to juju-core since this affects me, and I'm not using LXC containers at all. ** Package changed: lxc (Ubuntu) = juju-core (Ubuntu) ** Tags added: landscape -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
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 Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
** Changed in: juju-core Status: Confirmed = Triaged ** Changed in: juju-core Importance: Undecided = High ** Package changed: juju-core (Ubuntu) = maas ** Changed in: maas Status: Confirmed = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
** Summary changed: - Juju deploy of Charm in MAAS provider failing after successful bootstrap. Juju status stuck in “Pending” state + Juju deploy of Charm in MAAS fails because dbus fails ** Project changed: juju-core = lxc (Ubuntu) -- 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/ubuntu/+source/lxc/+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
Re: [Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Quoting Curtis Hovey (cur...@canonical.com): ** Summary changed: - Juju deploy of Charm in MAAS provider failing after successful bootstrap. Juju status stuck in “Pending” state + Juju deploy of Charm in MAAS fails because dbus fails Based on what I see in the machine.log, it looks like dbus was not installed. This is curious since AIUI juju uses the ubuntu-cloud image. When I install a precise ubuntu-cloud container, /var/run/dbus/system_bus_socket does exist. With ubuntu containers, it does not until I 'apt-get install dbus.' Could you please re-run this and, while the container is hung, log in with 'sudo lxc-console -n container-name', and see whether the dbus package is installed? status: incomplete ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- 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/ubuntu/+source/lxc/+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
Re: [Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Sorry, I see now that you ssh in to start dbus, so obviously it's installed. status: new ** Changed in: lxc (Ubuntu) Status: Incomplete = New -- 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/ubuntu/+source/lxc/+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
[Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
** Summary changed: - Juju deploy of Charm in MAAS provider failing after successful bootstrap. Juju status stuck in “Pending” state + Juju deploy of Charm in MAAS fails because dbus fails ** Project changed: juju-core = lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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/ubuntu/+source/lxc/+bug/1248283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Quoting Curtis Hovey (cur...@canonical.com): ** Summary changed: - Juju deploy of Charm in MAAS provider failing after successful bootstrap. Juju status stuck in “Pending” state + Juju deploy of Charm in MAAS fails because dbus fails Based on what I see in the machine.log, it looks like dbus was not installed. This is curious since AIUI juju uses the ubuntu-cloud image. When I install a precise ubuntu-cloud container, /var/run/dbus/system_bus_socket does exist. With ubuntu containers, it does not until I 'apt-get install dbus.' Could you please re-run this and, while the container is hung, log in with 'sudo lxc-console -n container-name', and see whether the dbus package is installed? status: incomplete ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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/ubuntu/+source/lxc/+bug/1248283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1248283] Re: Juju deploy of Charm in MAAS fails because dbus fails
Sorry, I see now that you ssh in to start dbus, so obviously it's installed. status: new ** Changed in: lxc (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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/ubuntu/+source/lxc/+bug/1248283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
