[Bug 1727355] Re: Juju attempts to bootstrap bionic by default

Bryan Quigley bryan.quigley at canonical.com
Thu Oct 26 14:52:38 UTC 2017


>We could change Juju code to hard code the preferred LTS as one we know
works but this means we need to change Juju each time we want to update
the preferred LTS.

I strongly prefer an approach where what version of Ubuntu deployed
doesn't change on release dates. (similar breakage happened to MAAS in
the past https://bugs.launchpad.net/maas/+bug/1573046)

My preference would be if you are on an LTS version of Ubuntu, use that
version.  If not, use a hardcoded Juju-team preferred version.  I'm not
sure I'd want stable versions of Juju to ever silently change what they
deploy.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to distro-info-data in Ubuntu.
https://bugs.launchpad.net/bugs/1727355

Title:
  Juju attempts to bootstrap bionic by default

Status in juju:
  Fix Released
Status in distro-info-data package in Ubuntu:
  Won't Fix
Status in distro-info-data source package in Trusty:
  Won't Fix
Status in distro-info-data source package in Xenial:
  In Progress
Status in distro-info-data source package in Zesty:
  In Progress
Status in distro-info-data source package in Artful:
  Won't Fix

Bug description:
  This is with 2.2.5 on xenial, with x86 hosts:

  I'm hitting this everytime I try to bootstrap:

  14:01:42 DEBUG juju.cmd.juju.commands bootstrap.go:497 (error details:
  [{github.com/juju/juju/cmd/juju/commands/bootstrap.go:588: failed to
  bootstrap model} {github.com/juju/juju/tools/list.go:19: no matching
  agent binaries available}])

  Full error:
  http://paste.ubuntu.com/25817026/

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1727355/+subscriptions



More information about the foundations-bugs mailing list