| 2016-03-31 23:57:24 |
Martin Packman |
bug |
|
|
added bug |
| 2016-04-01 00:15:22 |
Richard Harding |
description |
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. |
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. |
|
| 2016-04-01 00:15:49 |
Richard Harding |
description |
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. |
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. |
|
| 2016-04-01 00:16:03 |
Richard Harding |
description |
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. |
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. |
|
| 2016-04-01 00:16:20 |
Richard Harding |
bug task added |
|
juju-core |
|
| 2016-04-01 00:16:54 |
Richard Harding |
bug task deleted |
juju-core |
|
|
| 2016-04-04 21:34:40 |
Nicholas Skaggs |
bug task added |
|
juju-core |
|
| 2016-04-05 14:01:24 |
Curtis Hovey |
tags |
|
packaging |
|
| 2016-04-05 14:01:32 |
Curtis Hovey |
summary |
After upgrade Juju 1.X should still be the default |
After dist upgrade Juju 1.X should still be the default |
|
| 2016-04-08 02:54:12 |
Cheryl Jennings |
juju-core: status |
New |
Triaged |
|
| 2016-04-08 02:54:15 |
Cheryl Jennings |
juju-core: importance |
Undecided |
Critical |
|
| 2016-04-08 02:54:20 |
Cheryl Jennings |
juju-core: milestone |
|
2.0-beta4 |
|
| 2016-04-13 02:52:34 |
Cheryl Jennings |
juju-core: milestone |
2.0-beta4 |
2.0-rc1 |
|
| 2016-04-20 13:53:59 |
Curtis Hovey |
juju-core: milestone |
2.0-beta5 |
2.0-rc1 |
|
| 2016-04-20 15:10:46 |
Nicholas Skaggs |
juju-core: status |
Triaged |
Fix Released |
|
| 2016-04-20 15:10:56 |
Nicholas Skaggs |
juju-core (Ubuntu): status |
New |
Fix Released |
|
| 2016-08-23 01:05:24 |
Canonical Juju QA Bot |
affects |
juju-core |
juju |
|
| 2016-08-23 01:05:24 |
Canonical Juju QA Bot |
juju: milestone |
2.0-beta6 |
|
|
| 2016-08-23 01:05:26 |
Canonical Juju QA Bot |
juju: milestone |
|
2.0-beta6 |
|
