[Bug 1564670] [NEW] After upgrade Juju 1.X should still be the default
Martin Packman
martin.packman at canonical.com
Thu Mar 31 23:57:24 UTC 2016
Public bug reported:
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.
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
--
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/1564670
Title:
After upgrade Juju 1.X should still be the default
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1564670/+subscriptions
More information about the Ubuntu-server-bugs
mailing list