Comment 1 for bug 1130673

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.