autoload credentials has misleading error message when lxd not found

[David Lawson]

While trying to load a new set of credentials from Azure, we're consistently getting an error involving LXD:

~$ azure login
info: Executing command login
<snip>
info: login command OK
~$ juju autoload-credentials

Looking for cloud and credential information locally...
ERROR unable to detect local LXC credentials: failed to connect to local LXD: LXD socket not found; is LXD installed & running?

Please install LXD by running:
 $ sudo snap install lxd
and then configure it with:
 $ newgrp lxd
 $ lxd init

No cloud credentials found.
~$ juju --version
2.6.10-trusty-amd64

Why is it trying to find LXD creds and how do we make it stop? Related, how do we get it to find our actual Azure creds?

[Ian Booth (wallyworld)]

For now you can work around by using add-credential and manually enter the Azure credential details.

[Ian Booth (wallyworld)]

autoload-credentials is a convenience utility that loops across all providers to find any locally stored credentials to import those into juju, allowing to user to avoid manually entering the credential attributes. The fact that it errors when lxd is not installed is a bug for sure.

[Heather Lanigan (hmlanigan)]

"ERROR unable to detect local LXC..." is a log message and not returned as an error. Seeing the message here is highly misleading and will be addressed.

For azure, it looks like the credentials were not found. I will looking into why that was.

[Heather Lanigan (hmlanigan)]

@David, please run 'juju autoload-credentials --debug' after the 'az login'. I wonder if you're hitting this bug: https://bugs.launchpad.net/juju/+bug/1869939 ?

[Heather Lanigan (hmlanigan)]

Changing the error log message to debug: https://github.com/juju/juju/pull/11766

[Heather Lanigan (hmlanigan)]

log message pr merged into 2.8