** Changed in: juju-core
Status: Triaged => Invalid
--
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/1557345
Title:
xenial juju 1.25.3 unable to deploy to lxc containers
To
** Also affects: juju-core/1.25
Importance: Undecided
Status: New
** Changed in: juju-core/1.25
Status: New => Triaged
** Changed in: juju-core/1.25
Importance: Undecided => Critical
** Changed in: juju-core/1.25
Assignee: (unassigned) => Anastasia (anastasia-macmood)
*
Looks like we need to backport tych0's PR which changes the container
detection code:
https://github.com/juju/juju/commit/24fef1aeb33bd31a247be5e1f67b70ed734b9369
IIRC, that introduced some CI failures which were fixed in later
commits, so it's not a straightforward cherry-pick.
** Changed in: ju
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Status: New => Invalid
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => High
--
You received this bug notification because
** Changed in: juju-core
Milestone: 2.0-alpha3 => 2.0-beta4
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1500981
Title:
juju-db segfault while syncing with replicas
To m
** Changed in: juju-core
Milestone: 2.0-alpha3 => 2.0-beta4
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in sy
** Description changed:
The Juju team is preparing for a 2.0-beta1 release in time for the
xenial feature freeze date (18-Feb), but not all features required for
2.0 will be ready by that date. We believe we will have a complete and
stable Juju 2.0 by the time of the xenial release, but w
Public bug reported:
The Juju team is preparing for a 2.0-beta1 release in time for the
xenial feature freeze date (18-Feb), but not all features required for
2.0 will be ready by that date. We believe we will have a complete and
stable Juju 2.0 by the time of the xenial release, but we need to
r
** Changed in: juju-core
Milestone: 2.0-alpha2 => 2.0-alpha3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1500981
Title:
juju-db segfault while syncing with replicas
To
** Changed in: juju-core
Milestone: 2.0-alpha2 => 2.0-alpha3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in s
The script to address this bug is here:
http://paste.ubuntu.com/14474251/
Steps to resolve this issue:
- On the state server, install mongodb-clients (installs the mongo tool to
allow us to manually modify the database)
- Run the insert-statuses.sh script on the state server (machine 0):
./inser
Not fixing in 2.0, as users will be required to upgrade to 1.25.2 before
upgrading to 2.0
** Changed in: juju-core
Status: In Progress => Invalid
** Changed in: juju-core
Status: Invalid => Won't Fix
** Changed in: juju-core
Status: Won't Fix => Invalid
--
You received thi
** Changed in: juju-core
Milestone: 1.26-beta1 => 2.0-alpha2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1500981
Title:
juju-db segfault while syncing with replicas
To
** Changed in: juju-core
Milestone: 1.26-beta1 => 2.0-alpha2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in s
** Changed in: juju-core
Milestone: 1.26-alpha3 => 2.0-alpha1
--
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/1516989
Title:
juju status broken
To manage notifications about
Just a note to those using the script to insert the workload status -
you'll see a bogus time in the "since" field: 31 Dec 1969
18:00:00-06:00
--
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.
** Also affects: juju-core/1.25
Importance: Undecided
Status: New
** Changed in: juju-core/1.25
Status: New => Fix Committed
** Changed in: juju-core/1.25
Importance: Undecided => Critical
** Changed in: juju-core/1.25
Assignee: (unassigned) => Jesse Meek (waigani)
** C
The fix for this is underway, and should be included in 1.25.2.
William kindly put together a script to directly modify mongo to add in
the missing statuses to work around this problem in the meantime. You
can contact me directly to get the script until I figure out where to
put it.
I have verif
** Changed in: juju-core
Assignee: Cheryl Jennings (cherylj) => Jesse Meek (waigani)
--
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/1516989
Title:
juju status broken
fwereade is working on a script to repair an environment after this is
hit in an upgrade.
--
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/1516989
Title:
juju status broken
To man
I agree that we cannot move juju 1.25.1 out of proposed until the issue
is resolved. Discussions between dimitern and mpontillo indicate that
this is a maas 1.9beta2+ regression which changes in juju 1.25.1
exposed.
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: juju-core
Milestone: 1.26-alpha2 => 1.26-beta1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1500981
Title:
juju-db segfault while syncing with replicas
To
** Changed in: juju-core
Milestone: 1.26-alpha2 => 1.26-beta1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in
Bug #1515463 reveals that this change broke Juju. Marking as
verification failed.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.laun
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
Status: Triaged => Invalid
--
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/1510619
Serge - your changes from comment #22 will break juju with lxc. juju
will need to be modified to call systemctl add-wants multi-user.target
lxc.service
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchp
Verified that Juju can start lxc containers with the proposed changes.
The containers came up and were able to communicate with the state
server, even when on a separate machine.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ub
Kicked off instances for testing with Juju. Will update with results
once my testing is complete.
--
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/1509414
Title:
pre-installed lxc in cl
28 matches
Mail list logo
