I've got a juju controller on 3.3 deployed on a manual cloud.
I then tried to add an existing lxd cloud. I had to use "--force" in the command to add the cloud.
juju add-cloud -f ./mycloud.yaml --force"
After that, the cloud (mycloud) doesn't appear in juju clouds, and I also get a "Permission denied" in juju from trying run "juju clouds".
Only after removing the cloud (juju remove-cloud) the command works again.
Since I need this cloud to be able to migrate models from 2.9 -> 3.3 this is a critical bug preventing me from moving forward.
I've got a juju controller on 3.3 deployed on a manual cloud.
I then tried to add an existing lxd cloud. I had to use "--force" in the command to add the cloud.
juju add-cloud -f ./mycloud.yaml --force"
After that, the cloud (mycloud) doesn't appear in juju clouds, and I also get a "Permission denied" in juju from trying run "juju clouds".
Only after removing the cloud (juju remove-cloud) the command works again.
Since I need this cloud to be able to migrate models from 2.9 -> 3.3 this is a critical bug preventing me from moving forward.