@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
<4>init: Disconnected from system bus
<4>init: whoopsie main process ended, respawning
networking start/running
ubuntu@cloud1:~$ sudo
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 deconfigurin
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:/
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(s
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
** 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 a
** 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 abo
** 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:
http
** 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)
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 m
** 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
Bug
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 no
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 b
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.l
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
Im
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 d
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/1
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 l
** 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 mem
19 matches
Mail list logo
