** Tags added: cross-team-kanban 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/1557345
Title:
xenial juju 1.25.3 unable to deploy to lxc containers
To manage notificat
Manually tested fix on trusty, wily and xenial:
A. bootstrapped with default-series: "xenial"
juju add-machine lxc // PASSED, creating xenial
juju add-machine lxc --series=trusty // PASSED, creating trusty
juju add-machine lxc --series=wily // PASSED, creating wily
B. bootstrapped with
** Changed in: juju-core/1.25
Status: In Progress => Fix Committed
--
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
** Changed in: juju-core/1.25
Status: Triaged => In Progress
--
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 contai
Proposed fix against 1.25: https://github.com/juju/juju/pull/4754
--
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 containe
** 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
** Tags added: lxc xenial
--
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 manage notifications about this b
** 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
Note these are freshly bootstrapped clouds, as per an irc conversation
with alexisb and anastasiamac_.
I took a working juju environment deploying to canonistack, just changed the
default series, did a juju bootstrap and then a juju
deploy local:xenial/ubuntu --to lxc:0, and got an error as abov
** Tags added: canonical-bootstack
--
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 manage notifications abo
12 matches
Mail list logo