Activity log for bug #2049610

Date Who What changed Old value New value Message
2024-01-17 10:05:31 Erik Lönroth bug added bug
2024-01-17 10:05:31 Erik Lönroth attachment added juju clouds --all https://bugs.launchpad.net/bugs/2049610/+attachment/5740149/+files/Screenshot%20from%202024-01-17%2010-54-59.png
2024-01-17 10:08:09 Erik Lönroth description 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. clouds: dwellir17: type: lxd auth-types: [certificate] endpoint: https://192.168.108.10:8443 regions: sodertalje: endpoint: https://192.168.108.10:8443
2024-01-17 10:08:30 Erik Lönroth description 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. clouds: dwellir17: type: lxd auth-types: [certificate] endpoint: https://192.168.108.10:8443 regions: sodertalje: endpoint: https://192.168.108.10:8443 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
2024-02-01 10:35:46 Joseph Phillips juju: status New Triaged
2024-02-01 10:35:49 Joseph Phillips juju: importance Undecided Medium
2024-02-01 10:37:51 Vitaly Antonenko juju: assignee Caner Derici (cderici)