cert error on public controller: cannot validate certificate
Bug #1692905 reported by
Roger Peppe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Roger Peppe |
Bug Description
To reproduce:
juju login jaas
juju list-models
The error seen is:
ERROR cannot get model details: unable to connect to API: x509: cannot validate certificate for 162.213.33.28 because it doesn't contain any IP SANs
The logic in jujuclient is losing the public DNS name
in the APIAddresses field in the controller details
in controllers.yaml.
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I believe if we get a hostname we explicitly try to resolve it, and if that
fails we omit it. This is because MAAS frequently return hostnames that
only MAAS can resolve and not everyone configures their laptops to point at
MAAS DNS.
John
=:->
On May 23, 2017 18:10, "Roger Peppe" <email address hidden> wrote:
> Public bug reported: /bugs.launchpad .net/bugs/ 1692905 /bugs.launchpad .net/juju/ +bug/1692905/ +subscriptions
>
> To reproduce:
>
> juju login jaas
> juju list-models
>
> The error seen is:
>
> ERROR cannot get model details: unable to connect to API: x509:
> cannot validate certificate for 162.213.33.28 because it doesn't contain
> any IP SANs
>
>
> The logic in jujuclient is losing the public DNS name
> in the APIAddresses field in the controller details
> in controllers.yaml.
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> cert error on public controller: cannot validate certificate
>
> To manage notifications about this bug go to:
> https:/
>