juju tells me to "update" to earlier version
Bug #1974256 reported by
Jordan Barrett
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Ian Booth |
Bug Description
When you run a Juju 3 client with a Juju 2 controller, you get the following error:
```
ERROR juju client with major version 3 used with a controller having major version 2 not supported
update your juju client to match the version running on the controller
```
However, my client is already a later version than the controller, so updating is not going to help bridge the gap. What should we recommend here instead? Update the controller?
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 2.9.35 |
Changed in juju: | |
milestone: | 2.9.35 → 2.9.36 |
Changed in juju: | |
milestone: | 2.9.36 → 2.9.37 |
Changed in juju: | |
milestone: | 2.9.37 → 2.9.38 |
Changed in juju: | |
milestone: | 2.9.38 → 2.9.39 |
Changed in juju: | |
milestone: | 2.9.39 → 2.9.40 |
Changed in juju: | |
milestone: | 2.9.40 → 2.9.41 |
Changed in juju: | |
milestone: | 2.9.41 → 2.9.42 |
Changed in juju: | |
milestone: | 2.9.42 → 2.9.43 |
Changed in juju: | |
milestone: | 2.9.43 → 2.9.44 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
No, as of right now, you need to refresh your snap from the 2.9 track to match the controller version.
Although 2.9 clients are currently compatible with 3.0 controllers, as 3.0 evolves, this may not remain the case, ie we won't guarantee future 3.x controllers will stay compatible with 2.9 cli clients.
Things like migration, status, upgrades can be run with a 2.9 client though to help ease the transition.