See bug https://bugs.launchpad.net/juju-core/+bug/1564622 for the fix in
Juju to properly output the messaging to the user.
** Description changed:
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.
+ Feedback suggests that we should correct this by having juju 1.X be the
+ higher priority in update alternatives.
- There has been some concern that this is still too confusing and 1.X
- should remain the default juju without explicit user intervention.
+ Product management has give feedback that the preference it to push
+ toward the direction of Juju 2 at all times. Since this process would
+ default to Juju 1 if a Juju 2 users installs Juju 1 for legacy reasons,
+ we are instead going to implement the following:
+
+ $ 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.
** Description changed:
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:
Feedback suggests that we should correct this by having juju 1.X be the
higher priority in update alternatives.
Product management has give feedback that the preference it to push
toward the direction of Juju 2 at all times. Since this process would
default to Juju 1 if a Juju 2 users installs Juju 1 for legacy reasons,
we are instead going to implement the following:
- $ 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.
+ $ 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.
** Description changed:
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:
Feedback suggests that we should correct this by having juju 1.X be the
higher priority in update alternatives.
Product management has give feedback that the preference it to push
toward the direction of Juju 2 at all times. Since this process would
default to Juju 1 if a Juju 2 users installs Juju 1 for legacy reasons,
we are instead going to implement the following:
$ sudo apt-get update
- $ juju status
+
+ $ juju status
WARNING Creating new juju 2 configuration.
- Use `update-alternatives --config juju` to switch
- for 1.X environments.
- $ juju status
+ 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.
+ Please check your credentials or use 'juju bootstrap' to
+ create a new model.
** Also affects: juju-core
Importance: Undecided
Status: New
** No longer affects: juju-core
--
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
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
