[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
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
** 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
** 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
** 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
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
** 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
