Ubuntu
juju-core package

  1. Bug #1564670
  2. Comment #0

Comment 0 for bug 1564670

Revision history for this message
Martin Packman (gz) wrote : After upgrade Juju 1.X should still be the default

When upgrading to Xenial the new default Juju version is going to be 2.0.

Because 2.0 clients are not compatible with 1.X environments, this means existing environments will be inaccessible unless the 1.X client is switched to. The plan is to give a warning when creating Juju 2 configuration for the first time, something along the lines of:

$ sudo apt-get update
$ juju status
WARNING Creating new juju 2 configuration.
Use `update-alternatives --config juju` to switch for 1.X environments.
$ juju status
ERROR Unable to connect to model "".
Please check your credentials or use 'juju bootstrap' to create a new model.

There has been some concern that this is still too confusing and 1.X should remain the default juju without explicit user intervention.