I am finding that I am unable to remove anything less than a whole model. This is a consistent problem that keeps coming up.
If I try to remove something using the GUI, and commit, then everything looks like it went through correctly, but the graph shows that the thing I tried to remove is still there.
Similarly with the juju
command. juju remove-relation
and juju remove-application
both appear to work. (Return value 0, nothing printed), but nothing actually happens.
opentelco@dell02:~$ juju remove-relation neutron-api mysql --debug
23:50:53 INFO juju.cmd supercommand.go:57 running juju [2.5.4 gc go1.10.4]
23:50:53 DEBUG juju.cmd supercommand.go:58 args: []string{"/snap/juju/7206/bin/juju", "remove-relation", "neutron-api", "mysql", "--debug"}
23:50:53 INFO juju.juju api.go:67 connecting to API addresses: [10.58.2.36:17070]
23:50:53 DEBUG juju.api apiclient.go:888 successfully dialed "wss://10.58.2.36:17070/model/5cb0e921-1540-4b05-81d2-bf1f5e39ac4c/api"
23:50:53 INFO juju.api apiclient.go:608 connection established to "wss://10.58.2.36:17070/model/5cb0e921-1540-4b05-81d2-bf1f5e39ac4c/api"
23:50:53 DEBUG juju.api monitor.go:35 RPC connection died
23:50:53 INFO cmd supercommand.go:502 command finished
opentelco@dell02:~$ juju add-relation neutron-api mysql
cannot add relation "neutron-api:shared-db mysql:shared-db": relation neutron-api:shared-db mysql:shared-db already exists (already exists)
Is RPC connection died
a bad thing? It’s a DEBUG
message, so I am assuming that is expected behavior.
I can delete a whole model, then rebuild. When it try to remove a relation/app within the new model, the same thing happens.
juju --version
shows 2.5.4-bionic-amd64
. My controller and workload are deployed in MAAS.