juju deploy manila-generic failed

[Levente Tamás]

deployer@ic-infra1:~$ juju deploy manila-generic --channel ussuri/stable --debug
12:22:55 INFO juju.cmd supercommand.go:56 running juju [2.9.33 95186b2e0c2dfa9fe7b0b815cfe2c939813f9302 gc go1.18.5]
12:22:55 DEBUG juju.cmd supercommand.go:57 args: []string{"juju", "deploy", "manila-generic", "--channel", "ussuri/stable", "--debug"}
12:22:55 INFO juju.juju api.go:78 connecting to API addresses: [100.96.0.225:17070 100.96.0.231:17070 100.96.0.232:17070]
12:22:55 DEBUG juju.api apiclient.go:1153 successfully dialed "wss://100.96.0.225:17070/api"
12:22:55 INFO juju.api apiclient.go:688 connection established to "wss://100.96.0.225:17070/api"
12:22:55 INFO juju.juju api.go:78 connecting to API addresses: [100.96.0.225:17070 100.96.0.231:17070 100.96.0.232:17070]
12:22:55 DEBUG juju.api apiclient.go:1153 successfully dialed "wss://100.96.0.225:17070/model/310d5b98-8493-4e33-8161-060e0ef8ee7f/api"
12:22:55 INFO juju.api apiclient.go:688 connection established to "wss://100.96.0.225:17070/model/310d5b98-8493-4e33-8161-060e0ef8ee7f/api"
12:22:55 INFO juju.juju api.go:330 API endpoints changed from [100.96.0.225:17070 100.96.0.232:17070 100.96.0.231:17070] to [100.96.0.225:17070 100.96.0.231:17070 100.96.0.232:17070]
12:22:55 DEBUG juju.cmd.juju.application.deployer deployer.go:388 cannot interpret as local charm: file does not exist
12:22:55 DEBUG juju.cmd.juju.application.deployer deployer.go:207 cannot interpret as a redeployment of a local charm from the controller
12:22:56 DEBUG juju.cmd.juju.application.store charmadapter.go:142 cannot interpret as charmstore bundle: focal (series) != "bundle"
12:22:56 INFO cmd charm.go:452 Preparing to deploy "manila-generic" from the charmhub
12:22:57 INFO juju.cmd.juju.application.deployer series_selector.go:83 with the configured model default series "focal"
12:22:58 INFO cmd charm.go:537 Located charm "manila-generic" in charm-hub, revision 35
12:22:58 INFO cmd charm.go:236 Deploying "manila-generic" from charm-hub charm "manila-generic", revision 35 in channel ussuri/stable on focal
12:22:59 DEBUG juju.api monitor.go:35 RPC connection died
12:22:59 DEBUG juju.api monitor.go:35 RPC connection died
12:22:59 INFO cmd supercommand.go:544 command finished

[Levente Tamás (b823885)]

deployer@ic-infra1:~$ juju status manila-generic --relations
Model Controller Cloud/Region Version SLA Timestamp
openstack ic-controller-focal ic/default 2.9.33 unsupported 12:37:39Z

App Version Status Scale Charm Channel Rev Exposed Message
manila-generic unknown 0 manila-generic ussuri/stable 35 no

deployer@ic-infra1:~$ juju status manila --relations
Model Controller Cloud/Region Version SLA Timestamp
openstack ic-controller-focal ic/default 2.9.33 unsupported 12:37:30Z

App Version Status Scale Charm Channel Rev Exposed Message
manila 10.0.0 blocked 3 manila ussuri/stable 186 no No share backends configured
manila-mysql-router 8.0.35 active 3 mysql-router 8.0/stable 111 no Unit is ready

Unit Workload Agent Machine Public address Ports Message
manila/1* blocked idle 15/lxd/31 100.96.0.206 8786/tcp No share backends configured
  manila-mysql-router/2 active idle 100.96.0.206 Unit is ready
manila/2 blocked idle 16/lxd/30 100.96.0.207 8786/tcp No share backends configured
  manila-mysql-router/0* active idle 100.96.0.207 Unit is ready
manila/3 blocked idle 17/lxd/30 100.96.0.208 8786/tcp No share backends configured
  manila-mysql-router/1 active idle 100.96.0.208 Unit is ready

Machine State Address Inst id Series AZ Message
15 started 100.96.0.226 ic-hrzagt4-s4apy090 focal zone2 Deployed
15/lxd/31 started 100.96.0.206 juju-f8ee7f-15-lxd-31 focal zone2 Container started
16 started 100.96.0.193 ic-hrzagt4-s4apy059 focal zone1 Deployed
16/lxd/30 started 100.96.0.207 juju-f8ee7f-16-lxd-30 focal zone1 Container started
17 started 100.96.0.227 ic-hrzagt4-s4apy089 focal zone3 Deployed
17/lxd/30 started 100.96.0.208 juju-f8ee7f-17-lxd-30 focal zone3 Container started

Relation provider Requirer Interface Type Message
keystone:identity-service manila:identity-service keystone regular
manila-mysql-router:shared-db manila:shared-db mysql-shared subordinate
manila:cluster manila:cluster openstack-ha peer
mysql-innodb-cluster:db-router manila-mysql-router:db-router mysql-router regular
mysql-innodb-cluster:shared-db manila:shared-db mysql-shared regular
rabbitmq-server:amqp manila:amqp rabbitmq regular

[Alex Kavanagh (ajkavanagh)]

When you say "failed", what is the error message you are seeing, or the expected outcome that is not achieved, please?

[Levente Tamás (b823885)]

Both of them:
- there is an error message
- the expected outcome that is not achieved
(As I've sent already:
ic-hrzagt4 deployer@ic-hrzagt4-infra1:~$ juju status manila-generic --relations
Model Controller Cloud/Region Version SLA Timestamp
openstack ic-hrzagt4-controller-focal ic-hrzagt4/default 2.9.33 unsupported 09:16:12Z

App Version Status Scale Charm Channel Rev Exposed Message
manila-generic unknown 0 manila-generic ussuri/stable 35 no
)

[Alex Kavanagh (ajkavanagh)]

I'm not seeing an error message, other than the debug RPC teardown?

Did you do "juju add-relation manila manila-generic" to relate the subordinate manila-generic charm to manila?

Please could you show/describe the error message.

[Levente Tamás (b823885)]

deployer@ic-infra1:~$ juju add-relation manila manila-generic
ERROR ambiguous relation: "manila manila-generic" could refer to "manila-generic:juju-info manila:juju-info"; "manila:manila-plugin manila-generic:manila-plugin"; "manila:remote-manila-plugin manila-generic:manila-plugin"

[Levente Tamás (b823885)]

The relations should be done automatically by the charm.
But once it's running on error, this step is also not done.

[Alex Kavanagh (ajkavanagh)]

> The relations should be done automatically by the charm.
> But once it's running on error, this step is also not done.

No, that's not how it works. A subordinate charm needs to be "deployed" (essentially, added to the model), and then related (integrated in newer-speak) to the principle charm (in this case manila) for it to be added to the principle's unit. Deploying a subordinate charm doesn't add it to any units.

> deployer@ic-infra1:~$ juju add-relation manila manila-generic
> ERROR ambiguous relation: "manila manila-generic" could refer to "manila-generic:juju-info manila:juju-info"; "manila:manila-plugin manila-generic:manila-plugin"; "manila:remote-manila-plugin manila-generic:manila-plugin"

This just means that you need to do (after the manila-generic charm is deployed):

    juju add-relation manila:manila-plugin manila-generic:manila-plugin

That will resolve the correct relation and then add the manila-generic subordinate unit to (all of) the manila unit(s).

Note this, though from the manila-generic readme:

> This charm exists to provide an example backend for Manila, for the purpose of test and reference. It is NOT intended for production use in any case.

Please be sure that this is the subordinate charm that you wish to use. If it's for testing it is fine, but otherwise, it's not a production charm. Thanks.