LXD credential doesn't support public TLS certs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Ian Booth |
Bug Description
stgraber@
Only clouds with registered credentials are shown.
There are more clouds, use --all to see them.
You can bootstrap a new controller using one of these clouds...
Clouds available on the client:
Cloud Regions Default Type Credentials Source Description
cluster 1 default lxd 0 built-in LXD Cluster
cluster-admin 1 default lxd 0 built-in LXD Cluster
juju-cluster 1 default lxd 0 built-in LXD Cluster
localhost 1 default lxd 0 built-in LXD Cluster
n-contest 1 default lxd 0 built-in LXD Cluster
n-ctf 1 default lxd 0 built-in LXD Cluster
n-infra 1 default lxd 0 built-in LXD Cluster
n-team000 1 default lxd 0 built-in LXD Cluster
s-athos 1 default lxd 0 built-in LXD Cluster
s-c2400 1 default lxd 0 built-in LXD Cluster
s-delmak 1 default lxd 0 built-in LXD Cluster
s-rpi 1 default lxd 0 built-in LXD Cluster
s-sateda 1 default lxd 0 built-in LXD Cluster
s-vagonbrei 1 default lxd 0 built-in LXD Cluster
s-vorash 1 default lxd 0 built-in LXD Cluster
stgraber@
ERROR unable to read certificate from /home/stgraber/
ERROR unable to read certificate from /home/stgraber/
ERROR more than one credential detected
run juju autoload-
also it's incorrectly reporting ERROR for remotes that do not have a server certificate (because they use a valid public TLS cert)
Changed in juju: | |
assignee: | nobody → Ian Booth (wallyworld) |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Stefan submitted a fix here
https:/ /github. com/juju/ juju/pull/ 12330
Needs to be targetted to 2.8 and unit tests added.