machine fails to start with "connection permanently impossible" error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
In a prodstack model I had a machine that gave up whilst being provisioned with the following error:
2018-12-11 11:54:20 DEBUG juju.worker.
This seems to indicate that the agent couldn't log in to the controller, as I understand it this should not happen.
For completeness the entire machine log is:
2018-12-11 11:54:19 INFO juju.cmd supercommand.go:56 running jujud [2.4.7 gc go1.11.2]
2018-12-11 11:54:19 DEBUG juju.cmd supercommand.go:57 args: []string{
2018-12-11 11:54:19 DEBUG juju.utils gomaxprocs.go:24 setting GOMAXPROCS to 1
2018-12-11 11:54:19 DEBUG juju.agent agent.go:545 read agent config, format "2.0"
2018-12-11 11:54:19 INFO juju.worker.
2018-12-11 11:54:19 DEBUG juju.worker.
2018-12-11 11:54:19 DEBUG juju.worker.
2018-12-11 11:54:19 DEBUG juju.worker.
2018-12-11 11:54:19 DEBUG juju.worker.
2018-12-11 11:54:19 DEBUG juju.worker.
2018-12-11 11:54:19 DEBUG juju.worker.
2018-12-11 11:54:19 DEBUG juju.worker.
2018-12-11 11:54:19 DEBUG juju.worker.
2018-12-11 11:54:19 DEBUG juju.worker.
2018-12-11 11:54:19 DEBUG juju.worker.
2018-12-11 11:54:19 DEBUG juju.worker.
2018-12-11 11:54:19 DEBUG juju.worker.
2018-12-11 11:54:19 DEBUG juju.api apiclient.go:883 successfully dialed "wss://
2018-12-11 11:54:19 INFO juju.api apiclient.go:603 connection established to "wss://
2018-12-11 11:54:20 DEBUG juju.worker.
2018-12-11 11:54:20 DEBUG juju.worker.
2018-12-11 11:54:20 INFO juju.agent uninstall.go:36 marking agent ready for uninstall
2018-12-11 11:54:20 DEBUG juju.worker.
2018-12-11 11:54:20 DEBUG juju.worker.
2018-12-11 11:54:20 DEBUG juju.worker.
2018-12-11 11:54:20 DEBUG juju.worker.
2018-12-11 11:54:20 DEBUG juju.worker.
2018-12-11 11:54:20 DEBUG juju.worker.
2018-12-11 11:54:20 DEBUG juju.worker.
2018-12-11 11:54:20 DEBUG juju.worker.
2018-12-11 11:54:20 INFO juju.worker.
2018-12-11 11:54:20 DEBUG juju.worker.
2018-12-11 11:54:20 INFO juju.agent uninstall.go:47 agent already marked ready for uninstall
2018-12-11 11:54:20 INFO juju.cmd.jujud machine.go:1238 uninstalling agent
2018-12-11 11:54:20 DEBUG juju.service discovery.go:115 discovered init system "systemd" from local host
2018-12-11 11:54:20 DEBUG juju.cmd.jujud introspection.go:72 engine stopped, stopping introspection
2018-12-11 11:54:20 DEBUG juju.worker.
2018-12-11 11:54:20 DEBUG juju.worker.
2018-12-11 11:54:20 DEBUG juju.worker.
2018-12-11 11:54:20 DEBUG juju.cmd.jujud introspection.go:75 introspection stopped
2018-12-11 11:54:20 DEBUG juju.service.
2018-12-11 11:54:20 DEBUG juju.service discovery.go:115 discovered init system "systemd" from local host
2018-12-11 11:54:20 DEBUG juju.service.
2018-12-11 11:54:20 DEBUG juju.service.
2018-12-11 11:54:20 INFO cmd supercommand.go:465 command finished
2018-12-11 11:54:20 DEBUG juju.cmd.jujud main.go:201 jujud complete, code 0, err <nil>
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
I've seen the same issue: https:/ /paste. ubuntu. com/p/T5zdbRSXm Y/