autoload credentials has misleading error message when lxd not found
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Heather Lanigan |
Bug Description
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-
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?
Changed in juju: | |
milestone: | 2.7.2 → 2.7.3 |
Changed in juju: | |
milestone: | 2.7.3 → 2.7.4 |
Changed in juju: | |
milestone: | 2.7.4 → 2.7.5 |
Changed in juju: | |
milestone: | 2.7.5 → 2.7.6 |
Changed in juju: | |
milestone: | 2.7.6 → 2.8.1 |
tags: | added: autoload-credentials |
Changed in juju: | |
assignee: | nobody → Heather Lanigan (hmlanigan) |
summary: |
- autoload credentials fails with weird LXD error + autoload credentials has misleading error message when lxd not found |
Changed in juju: | |
status: | Triaged → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
For now you can work around by using add-credential and manually enter the Azure credential details.