sshclient needs to handle ssh errors
Bug #616817 reported by
Kapil Thangavelu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Fix Released
|
Medium
|
Kapil Thangavelu | ||
Bug Description
The ssh client needs to handle error conditions in establishing the ssh tunnel, for example when connecting if key auth fails, or the remote host is not up, the ssh tunnel can never be established, but this isn't communicated to the client which is still attempting to connect even though its hopeless that it will work till the connect timeout is reached. Ideally errors on the ssh tunnel would be propogated to the connect deferred result to cause an error condition.
In addition to handling errors, sshclient should also wait for the SSH tunnel to be established before firing the deferred to its caller. This work is being tracked in bug #613990.
Revision history for this message
| Kapil Thangavelu (hazmat) wrote | #1 |
| Changed in ensemble: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| description: | updated |
| Changed in ensemble: | |
| milestone: | none → 0.1 |
| assignee: | nobody → Kapil Thangavelu (hazmat) |
| status: | Confirmed → In Progress |
| Changed in ensemble: | |
| status: | In Progress → Fix Committed |
| Changed in ensemble: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Looks like this is related to bug 613990
In the functional test it looks like there is still a race condition before the ssh key is put into place via cloud-init and when we connect.