** Changed in: juju-core (Ubuntu)
Milestone: vivid-updates => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409639
Title:
juju needs to support systemd for >= vivid
To manage notification
** Changed in: juju-core (Ubuntu Vivid)
Status: Fix Committed => Fix Released
** Changed in: juju-core (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Changed in: juju-core (Ubuntu Vivid)
Status: In Progress => Fix Committed
** Changed in: juju-core (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Tags added: systemd vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409639
Title:
juju needs to support systemd for >= vivid
To manage notifications about this bug go to:
https://bugs.launc
** Changed in: juju-core (Ubuntu Vivid)
Milestone: ubuntu-15.04 => vivid-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409639
Title:
juju needs to support systemd for >= vivid
To manag
https://github.com/juju/juju/commit/2ae93fe45df4b95bedf493adc07ee7049859fb2d
also has some serious deficiencies, see Dimitri's comments.
** Changed in: juju-core (Ubuntu Vivid)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bu
I also don't understand why this is marked Fix Released, upstream I only
see systemd/centos support and no systemd/ubuntu support. I see code
that assumes ubuntu == upstart.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Changed in: juju-core (Ubuntu Vivid)
Milestone: ubuntu-15.01 => ubuntu-15.04
** Changed in: juju-core (Ubuntu Vivid)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Changed in: juju-core
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409639
Title:
juju needs to support systemd for >= vivid
To manage notifications
** Tags added: hs-arm64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409639
Title:
juju needs to support systemd for >= vivid
To manage notifications about this bug go to:
https://bugs.launchpad.
Thanks Robie for the summary. For the record, if you want to continue
running the DEP-8 tests in an upstart environment under vivid, you can
do that at the top of your test:
if [ -d /run/systemd/system ]; then
if [ ! -x /tmp/autopkgtest-reboot ]; then
echo "SKIP: testbed does not suppo
** Description changed:
+ [Status]
+
+ The status of Juju and systemd need to be considered in three separate
+ scenarios:
+
+ A: A system administrator running the Juju client. For example, managing
+ a deployment somewhere else from your laptop.
+
+ B: Running within a deployment itself (the
It will also be worth looking into the impact of systemd on existing
charms that get published for vivid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409639
Title:
juju needs to support systemd f
> Which upstream release are you expecting us to pull in to Vivid to fix
this please?
As Juju has a "newer versions allowed" exception even for stables, that
should equally apply to the current development series. So while I'm not
officially in ~ubuntu-release, I'd say "whichever one works" is an
We have 1.20.14 in Vivid at the moment, and dep8 tests are now failing.
I believe this is because the systemd switch has happened, and it cannot
find upstart.
Which upstream release are you expecting us to pull in to Vivid to fix
this please?
--
You received this bug notification because you are
** Changed in: juju-core
Milestone: 1.23 => 1.23-beta1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409639
Title:
juju needs to support systemd for >= vivid
To manage notifications about this
the last of the patches to add systemd support in juju (including on
vivid) has landed. There are a couple of caveats we need to look into
though:
* vivid LXC containers on non-vivid hosts don't work correctly out of the box.
This has an impact on local provider (I've been testing in a vivid KV
@Eric,
Thanks for the comment. To confirm is this still on track for 1.23 and
the Ubuntu 15.04 (Vivid) release?
-thanks,
Antonio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409639
Title:
juju n
We've landed a patch for systemd support in juju. We are currently
working through a couple of minor bugs before calling it good.
** Changed in: juju-core
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Looking at http://reviews.vapour.ws/r/671/ it looks very bad.
Please use DBus api to talk to systemd.
Or use golang-go-systemd-dev to operate against systemd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Right now we (juju core) are scoping out the effort to add systemd
support to juju in time for the feature freeze. We'll update here as we
move forward.
Note that, as Andrew said, we have some of the work done already (though
not merged yet). It's likely the trickiest part, so the remainder of
t
Feature freeze isn't until Mid-February, so any new feature can be put
into the vivid package without problems by then. Even after that this
will certainly get a freeze exception as this is a release goal. But as
this apparently blocks OpenStack deployment/testing (said James Page),
we'd probably b
We have frozen juju 1.22. We expect it to ship with vivid. This feature
will need to be back-ported. How does Ubuntu feel about adding a feature
to 1.22.1? If this is bad, then we will wait for 1.23 to be backported
to w, v and t.
** Changed in: juju-core
Milestone: None => 1.23
** Changed in
Systemd support is currently under development, primarily to support
CentOS: http://reviews.vapour.ws/r/671/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409639
Title:
juju needs to support system
(I should have added: but will support Ubuntu, with a couple of minor
adjustments)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409639
Title:
juju needs to support systemd for >= vivid
To manage
** Tags added: systemd-boot
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Milestone: None => ubuntu-15.01
** Changed in: juju-core (Ubuntu)
Status: New => Triaged
** Changed in: juju-core (Ubuntu)
Importance: Unde
26 matches
Mail list logo
