| 2017-03-03 16:57:01 |
Charles Butler |
description |
When I attempt to debug a bootstrap failure that is ssh related, passing --debug is usually not as useful as it could be. We don't appear to have any way to indicate to juju that we need the extra level of verbose output to the ssh command.
What I propose is to extend the --debug flag to also place ssh in extra verbose mode "ssh -vvv" so we can see the handoff and key exchange between the workstation and the host to help indicate if there are issues during the connection phase.
Otherwise we can be left in a scenario where the only thing we see is:
"Attempting to connect to 192.168.1.137" or similar, with no real indicator what is/has gone wrong during the bootstrap phase with regards to ssh connectivity. |
When I attempt to debug a bootstrap failure that is ssh related, passing --debug is not as helpful as it could be. We don't appear to have any way to indicate to juju that we need the extra level of verbose output to the ssh command.
What I propose is to extend the --debug flag to also place ssh in extra verbose mode "ssh -vvv" so we can see the handoff and key exchange between the workstation and the host to help indicate if there are issues during the connection phase.
Otherwise we can be left in a scenario where the only thing we see is:
"Attempting to connect to 192.168.1.137" or similar, with no real indicator what is/has gone wrong during the bootstrap phase with regards to ssh connectivity. |
|
