Juju refresh from ch -> local charm fails with: unknown option "trust"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Harry Pidcock |
Bug Description
I have installed the latest microk8s charm from charmhub, and wanted to make a change and try it out from a local charm:
Starting here:
Model Controller Cloud/Region Version SLA Timestamp
microk8s addyess-vsphere vsphere/Boston 3.1.0 unsupported 11:58:52-05:00
App Version Status Scale Charm Channel Rev Exposed Message
microk8s active 1 microk8s stable 35 no
Unit Workload Agent Machine Public address Ports Message
microk8s/1* active idle 1 10.246.154.140 80,443,16443/tcp
Machine State Address Inst id Base AZ Message
1 started 10.246.154.140 juju-dff66a-1 ubuntu@20.04 poweredOn
-------
❯ juju refresh microk8s --switch ./*.charm --debug --verbose
11:55:57 INFO juju.cmd supercommand.go:56 running juju [3.1.2 f43d417390caeba
11:55:57 DEBUG juju.cmd supercommand.go:57 args: []string{
11:55:57 INFO juju.juju api.go:86 connecting to API addresses: [10.246.
11:55:57 DEBUG juju.api apiclient.go:1167 successfully dialed "wss://
11:55:57 INFO juju.api apiclient.go:702 connection established to "wss://
11:55:57 DEBUG juju.core.charm computedseries.
11:56:33 INFO cmd refresh.go:405 Added local charm "microk8s", revision 3, to the model
11:56:33 DEBUG juju.api monitor.go:35 RPC connection died
ERROR parsing config settings: unknown option "trust"
11:56:33 DEBUG cmd supercommand.go:548 error stack:
parsing config settings: unknown option "trust"
github.
github.
-------
Afterwards, the model isn't updated from the local version.
Here's a snippet of the controller log which mentions the same unknown option
-------
2023-04-20 17:03:45 DEBUG juju.state.
2023-04-20 17:03:45 DEBUG juju.apiserver request_
2023-04-20 17:03:45 DEBUG juju.apiserver request_
2023-04-20 17:03:45 DEBUG juju.apiserver admin.go:474 model login: user admin has "superuser" for controller; "admin" for model fd392a78-
2023-04-20 17:03:45 DEBUG juju.apiserver admin.go:409 model login: user-admin for fd392a78-
2023-04-20 17:03:45 DEBUG juju.apiserver request_
2023-04-20 17:03:46 DEBUG juju.apiserver request_
2023-04-20 17:03:46 DEBUG juju.apiserver request_
2023-04-20 17:03:46 DEBUG juju.state.
2023-04-20 17:03:46 DEBUG juju.state.
2023-04-20 17:03:46 DEBUG juju.apiserver request_
2023-04-20 17:03:46 DEBUG juju.apiserver request_
2023-04-20 17:03:46 DEBUG juju.apiserver request_
2023-04-20 17:03:46 DEBUG juju.apiserver request_
2023-04-20 17:03:46 DEBUG juju.apiserver request_
2023-04-20 17:03:46 DEBUG juju.apiserver request_
2023-04-20 17:03:46 DEBUG juju.apiserver request_
2023-04-20 17:03:46 DEBUG juju.apiserver request_
2023-04-20 17:03:47 DEBUG juju.apiserver request_
2023-04-20 17:03:48 DEBUG juju.apiserver request_
-------
Changed in juju: | |
milestone: | none → 3.1.3 |
importance: | Undecided → Critical |
status: | New → Triaged |
Changed in juju: | |
assignee: | nobody → Harry Pidcock (hpidcock) |
Changed in juju: | |
milestone: | 3.1.3 → 3.1.4 |
Changed in juju: | |
milestone: | 3.1.4 → 3.1.5 |
Changed in juju: | |
milestone: | 3.1.5 → 3.1.6 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
I've looked into this, the problem I can see here is that the juju 3.1.1 client introduced the --trust option, when your controller is running juju 3.1.0 which doesn't support that option. Since you didn't specify it, this is fixed by https:/ /github. com/juju/ juju/pull/ 15796 which fixes https:/ /bugs.launchpad .net/juju/ +bug/2019924