juju needs improved error messaging when controller has connection issues
Bug #1644011 reported by
Richard Harding
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
With the juju-db service stopped the user gets the following:
ERROR could not get controller info: cannot get controllers document: read tcp 10.20.3.
This is a case of mongodb being down and only knowing the port gives a hint as to where to go here. I think we should be able to do a better job detecting the root cause of this communication failure here.
tags: | added: usability |
Changed in juju: | |
importance: | High → Medium |
milestone: | 2.2.0-beta1 → none |
To post a comment you must log in.
Note that you can get warnings of these with multiple interfaces/ addresses on a controller as it'll connect to mongodb on the internal address but fail on the public address. When we update the error messaging we should also note the working condition smoother as well.