Paramiko: exception reading SSH protocol banner

Bug #1130673 reported by Max Brustkern
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
UTAH
Triaged
Medium
Max Brustkern

Bug Description

I'm seeing a new SSH error here:
http://10.97.0.1:8080/job/bootspeed-raring-desktop-amd64-acer-veriton-01/72/console

We should figure out what's causing this and what we can do about it. We should also catch this exception and report it differently.

Changed in utah:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Max Brustkern (nuclearbob) wrote :

This always seems to occur during the multiple reboots associated with checking whether the preparation testsuite has completed. I think we're just hitting the SSH server during an inconvenient part of the reboot process. I can think of three things to do about this:

1. Catch that exception and throw a UTAHException allowing the connection to be attempted again. We'll still stop trying after our existing timeout expires.
2. Get remote logging of client activity working, and then we can use that to determine that the testsuite is complete instead of trying SSH over and over.
3. Continue attempting to recreate this issue, possibly with extra verbose logging to attempt to more precisely correlate the network connection reset with logs on the system under test.

We can discuss these options in the next standup.

Andy Doan (doanac)
Changed in utah:
assignee: nobody → Max Brustkern (nuclearbob)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.