juju 3.0 client cannot refresh --switch from cs to ch on 2.9 controller
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
With a 2.9 juju client and controller
$ juju deploy cs:ubuntu csubuntu
Located charm "ubuntu" in charm-store, revision 21
Deploying "csubuntu" from charm-store charm "ubuntu", revision 21 in channel stable on xenial
If you then use a 3.0 juju client to refresh the charm:
$ juju refresh csubuntu --switch ch:ubuntu
ERROR series required for charm-hub charms (bad request)
17:08:29 TRACE juju.rpc.jsoncodec codec.go:227 -> {"request-
17:08:29 TRACE juju.rpc.jsoncodec codec.go:121 <- {"request-
17:08:29 INFO cmd refresher.go:336 Using channel "stable"
17:08:29 TRACE juju.rpc.jsoncodec codec.go:227 -> {"request-
17:08:29 TRACE juju.rpc.jsoncodec codec.go:121 <- {"request-
A 2.9 client succeeds:
$ juju refresh csubuntu --switch ch:ubuntu
Added charm-hub charm "ubuntu", revision 21 in channel stable, to the model
17:16:31 TRACE juju.rpc.jsoncodec codec.go:227 -> {"request-
17:16:31 TRACE juju.rpc.jsoncodec codec.go:121 <- {"request-
17:16:31 INFO cmd refresher.go:338 Using channel "stable"
17:16:31 TRACE juju.rpc.jsoncodec codec.go:227 -> {"request-
17:16:33 TRACE juju.rpc.jsoncodec codec.go:121 <- {"request-
17:16:33 INFO cmd refresh.go:441 Added charm-hub charm "ubuntu", revision 21 in channel stable, to the model
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: | |
milestone: | 2.9.44 → 2.9.45 |
Changed in juju: | |
milestone: | 2.9.45 → 2.9.46 |
The 2.9 client includes series in the AddCharm params, while the 3.0 client does not.
At the very least, the 3.0 client error message is extremely misleading.