failure to connect to maas endpoint looks the same as wrong maas version
Bug #1644395 reported by
Richard Harding
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
Bug Description
When Juju attempts to connect to maas it uses this logic:
"Try to connect to the 2.0 endpoint, if that times out or fails try to connect to the 1.0 endpoint. If that fails then tell the user we failed to connect to the url with /1.0/version in the url"
Debug output example:
https:/
Basically we need to indicate to the user that we tried to connect to 2.0 and failed. To the user it looks like Juju is trying to connect/auth to the wrong url endpoint (v1.0 vs v2.0) and so when it fails to communicate at all it looks like Juju was just being stupid.
We need this to fail more clearly with notes that we tried 2.0, that failed to connect, we tried 1.0 as a fallback, that timed out as well.
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.