Permission denied on "juju clouds" for user admin

[Erik Lönroth]

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.

This was the yaml used to add the cloud.

clouds:
  dwellir17:
    type: lxd
    auth-types: [certificate]
    endpoint: https://192.168.108.10:8443
    regions:
      sodertalje:
        endpoint: https://192.168.108.10:8443

[Joseph Phillips (manadart)]

What was the error that prevented addition of the cloud without "--force"?

[Erik Lönroth (erik-lonroth)]

I think it was "not supported" on manual clouds something...

[Joseph Phillips (manadart)]

We have a white-list of compatible cloud-on-cloud combinations. Where we won't guarantee support, such combinations require the use of "--force". That part is fine.

It seems apparent from reading through the logic that an "admin" user should be able to view the clouds on the controller. There is evidently a bug here.