juju quickstart should respect output of "juju api-endpoints"
Bug #1378264 reported by
Adam Collard
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-quickstart |
Fix Released
|
High
|
Francesco Banconi | ||
Bug Description
Trying to use Juju quickstart with MAAS when I'm not pointing at MAAS' DNS server fails because it uses the name of machine 0 instead of the IP addresses.
It should respect the output of juju api-endpoints (which has IPs and are reachable).
The error output I see is:
11:43:10 WARNING app@connect:307 Retrying: unable to connect to the Juju API server on wss://fermi.
Note juju api-endpoints says:
10.1.4.1:17070
Related branches
lp:~frankban/juju-quickstart/maas-address
- Juju GUI Hackers: Pending requested
-
Diff: 1288 lines (+332/-433)12 files modifiedREADME.rst (+2/-0)
quickstart/__init__.py (+1/-1)
quickstart/app.py (+21/-31)
quickstart/manage.py (+6/-11)
quickstart/settings.py (+3/-0)
quickstart/tests/helpers.py (+11/-0)
quickstart/tests/test_app.py (+63/-183)
quickstart/tests/test_manage.py (+19/-68)
quickstart/tests/test_utils.py (+18/-0)
quickstart/tests/test_watchers.py (+122/-108)
quickstart/utils.py (+14/-0)
quickstart/watchers.py (+52/-31)
Revision history for this message
| Francesco Banconi (frankban) wrote | #1 |
| Changed in juju-quickstart: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: cloud-installer |
Revision history for this message
| David Britton (dpb) wrote | #2 |
| Changed in juju-quickstart: | |
| assignee: | nobody → Francesco Banconi (frankban) |
| status: | Triaged → In Progress |
| Changed in juju-quickstart: | |
| status: | In Progress → Fix Committed |
| Changed in juju-quickstart: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is quickstart trying to connect to the GUI server (GUI unit) WebSocket. Since the GUI is co-located on the bootstrap node, it indeed shares the same Juju API server address (but using a different port/path). This bug is still valid: quickstart should be smarter when selecting the address to use to connect to the GUI unit.