We have the same behavior as @hypeitnow where it would upload the clients LXD server.crt instead of the given server cert. However, this problem occurs only for some clouds so I looked for any differences.
Working cloud:
defined: public
type: lxd
auth-types: [certificate]
endpoint: https://192.168.111.4:8443
credential-count: 1
regions:
sodertalje: {}
Not working cloud:
defined: public
type: lxd
auth-types: [certificate]
credential-count: 1
regions:
sodertalje:
endpoint: https://192.168.111.6:8443
See the difference here where the endpoint
is set. So for the “Not working cloud” I had to set --region sodertalje
for it to work. Example:
juju update-credential cloud9 --region sodertalje cloud9-credential