Canonical Juju

Bootstrap needs more console logging

Bug #1716730 reported by Nicholas Skaggs on 2017-09-12

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Canonical Juju	Fix Released	High	Ian Booth	Canonical Juju 2.3-beta1

Bug Description

Juju isn't descriptive about what is happening after it downloads the agent to the machine. Juju can sometimes fail to bootstrap after it has established ssh access and is running setup.

It would be useful to surface actual errors as well as status into the console output for the client so users can understand what is happening, and to make understanding errors / issues much easier.

Revision history for this message

Anastasia (anastasia-macmood) wrote on 2017-09-15:

@Nicholas Skaggs,
More verbose output, when desired, can be achieved with " --debug --show-log" options against bootstrap command.
Is this not enough?
If not, could you please provide a sample output of what you are getting AND what you'd prefer to see?

Changed in juju:
status:	New → Incomplete

Revision history for this message

Nicholas Skaggs (nskaggs) wrote on 2017-10-03:

Specifically, all operations done after the agent is downloaded, but before bootstrap is complete. During this time, we install things via apt and do other things on the remote system. This process is a bit of a black box from the client cli; no status is returned, no information about what's happening, and if it fails or gets stuck, no response or feedback from the client.

Revision history for this message

Ian Booth (wallyworld) wrote on 2017-10-03:

We don't have easy insight to the individual ssh script commands, and nor would we want to. But there's a few extra line of output that should be added around the execution of the ssh init script and bootstrap machine startup

Changed in juju:
milestone:	none → 2.3-alpha1
assignee:	nobody → Ian Booth (wallyworld)
status:	Incomplete → In Progress
importance:	Undecided → High