Suggest juju1 upon first use of juju2 if there is an existing JUJU_HOME dir
Bug #1564622 reported by
Cheryl Jennings
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Nate Finch |
Bug Description
Users with existing juju 1.x environments may be surprised when doing a dist upgrade if juju2 is the default in update-alternatives and they can no longer talk to their 1.x environments.
Juju2 can be updated to look for a JUJU_HOME dir upon first use (when creating JUJU_DATA), or when it can't find any information in JUJU_DATA to suggest that users can use update-alternatives to use juju1 to talk to existing environments.
Changed in juju-core: | |
assignee: | nobody → Nate Finch (natefinch) |
Changed in juju-core: | |
milestone: | 2.0-beta4 → 2.0-rc1 |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
milestone: | 2.0-beta5 → 2.0-rc1 |
Changed in juju-core: | |
milestone: | 2.0-rc1 → 2.0-beta5 |
Changed in juju-core: | |
status: | In Progress → Fix Released |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta5 → none |
milestone: | none → 2.0-beta5 |
To post a comment you must log in.
Update alternatives was removed in beta3, we should point users directly to the juju-1 location