I’ve never had an issue deploying ceph custers, then i’m suddenly running into this error
juju deploy -n 3 ceph-mon
ERROR resolve charms not supported
Any help is appreciated. 
Hi Dan, I’m sorry to hear you ran into a problem. I don’t see that problem here:
$ juju deploy ceph-mon
Located charm "ceph-mon" in charm-hub, revision 64
Deploying "ceph-mon" from charm-hub charm "ceph-mon", revision 64 in channel stable
My guess is that there was an outage with Charmhub and it was returning a temporary error. If you are still encountering this, can you include
juju --versionjuju deploy --debug -n 3 ceph-mon
Thanks.
Thanks so much jameinel. I was able to get around this by deploying the specific version juju deploy cs:ceph-osd-308 -n 3. I cannot get it to work in standard form however. Version and Debug listed below.
juju --version
2.9.0-ubuntu-amd64
juju deploy --debug -n 3 ceph-mon
11:22:28 INFO juju.cmd supercommand.go:56 running juju [2.9.0 0
ac860f7db4296273ea2cf213115ec2c229d57a07 gc go1.14.15]
11:22:28 DEBUG juju.cmd supercommand.go:57
args: []string{"/snap/juju/16132/bin/juju", "deploy", "--debug", "-n", "3", "ceph-mon"}
11:22:28 INFO juju.juju api.go:78 connecting to API addresses: [192.168.3.131:17070] 11:22:28 DEBUG juju.api apiclient.go:1132 successfully dialed "wss://192.168.3.131:17070/api" 11:22:28 INFO juju.api apiclient.go:664 connection established to "wss://192.168.3.131:17070/api"
11:22:28 INFO juju.juju api.go:78 connecting to API addresses: [192.168.3.131:17070] 11:22:28 DEBUG juju.api apiclient.go:1132 successfully dialed "wss://192.168.3.131:17070/model/b1e9fcf4-e5db-4719-85a8-9273bd85c3d5/api"
11:22:28 INFO juju.api apiclient.go:664 connection established to "wss://192.168.3.131:17070/model/b1e9fcf4-e5db-4719-85a8-9273bd85c3d5/api"
11:22:28 INFO juju.juju api.go:78 connecting to API addresses: [192.168.3.131:17070]
11:22:28 DEBUG juju.api apiclient.go:1132 successfully dialed "wss://192.168.3.131:17070/api"
11:22:28 INFO juju.api apiclient.go:664 connection established to "wss://192.168.3.131:17070/api"
11:22:28 DEBUG juju.cmd.juju.application.deployer deployer.go:396 cannot interpret as local charm: file does not exist
11:22:28 DEBUG juju.cmd.juju.application.deployer deployer.go:203 cannot interpret as a redeployment of a local charm from the controller
11:22:28 DEBUG juju.api monitor.go:35 RPC connection died ERROR resolve charms not supported
11:22:28 DEBUG cmd supercommand.go:537 error stack: /build/snapcraft-juju-35d6cf/parts/juju/src/api/charms/client.go:64: resolve charms not supported
/build/snapcraft-juju-35d6cf/parts/juju/src/cmd/juju/application/store/charmadapter.go:78:
/build/snapcraft-juju-35d6cf/parts/juju/src/cmd/juju/application/store/charmadapter.go:115:
/build/snapcraft-juju-35d6cf/parts/juju/src/cmd/juju/application/deployer/deployer.go:446: /build/snapcraft-juju-35d6cf/parts/juju/src/cmd/juju/application/deployer/deployer.go:72:/build/snapcraft-juju-35d6cf/parts/juju/src/cmd/juju/application/deploy.go:800:
Thanks for the response. So by default in juju 2.9 ‘juju deploy ceph-mon’ should be deploying from Charmhub rather than the old cs: charm store.
When I do the same deploy on a local LXD cluster I get:
07:33:42 INFO juju.cmd supercommand.go:56 running juju [2.9.0 0 ac860f7db4296273ea2cf213115ec2c229d57a07 gc go1.14.15]
07:33:42 DEBUG juju.cmd supercommand.go:57 args: []string{"/snap/juju/16132/bin/juju", "deploy", "-n", "3", "ceph-mon", "--debug"}
07:33:42 INFO juju.juju api.go:78 connecting to API addresses: [10.5.24.216:17070]
07:33:42 DEBUG juju.api apiclient.go:1132 successfully dialed "wss://10.5.24.216:17070/api"
07:33:42 INFO juju.api apiclient.go:664 connection established to "wss://10.5.24.216:17070/api"
07:33:42 INFO juju.juju api.go:78 connecting to API addresses: [10.5.24.216:17070]
07:33:42 DEBUG juju.api apiclient.go:1132 successfully dialed "wss://10.5.24.216:17070/model/dbf631c5-bcfe-4cbd-8070-1cbdc8de4b9d/api"
07:33:42 INFO juju.api apiclient.go:664 connection established to "wss://10.5.24.216:17070/model/dbf631c5-bcfe-4cbd-8070-1cbdc8de4b9d/api"
07:33:42 INFO juju.juju api.go:78 connecting to API addresses: [10.5.24.216:17070]
07:33:42 DEBUG juju.api apiclient.go:1132 successfully dialed "wss://10.5.24.216:17070/api"
07:33:42 INFO juju.api apiclient.go:664 connection established to "wss://10.5.24.216:17070/api"
07:33:42 DEBUG juju.cmd.juju.application.deployer deployer.go:396 cannot interpret as local charm: file does not exist
07:33:42 DEBUG juju.cmd.juju.application.deployer deployer.go:203 cannot interpret as a redeployment of a local charm from the controller
07:33:43 DEBUG juju.cmd.juju.application.store charmadapter.go:122 cannot interpret as charmstore bundle: xenial (series) != "bundle"
07:33:43 INFO cmd charm.go:435 Preparing to deploy "ceph-mon" from the charm-hub
07:33:44 INFO cmd charm.go:512 Located charm "ceph-mon" in charm-hub, revision 66
07:33:44 INFO cmd charm.go:237 Deploying "ceph-mon" from charm-hub charm "ceph-mon", revision 66 in channel stable
07:33:45 DEBUG juju.api monitor.go:35 RPC connection died
07:33:45 INFO cmd supercommand.go:544 command finished
Is your controller actually a 2.8 controller? (juju status or juju controllers should report the agent versions) I wonder if the client and controller are getting confused as to where the charm should be coming from.
Good call. juju controllers is reporting It is actually version 2.8.10
Reported Bug #1927091 “juju 2.9 doesn't deploy against charmstore for a 2...” : Bugs : juju
In the short term there are a few workarounds
- be specific, both 2.8 and 2.9 support explicitly targeting the charm store with
juju deploy cs:ceph-mon. You don’t have to specify an explicit revision - switch your client
sudo snap refresh juju --channel 2.8