Comment 2 for bug 662482

We do have an error here, which is masking the original error. It seems that the code assumes "e.args[0]" is always a string, but in this case it is an integer.

Offhand, it looks like something is raising a custom exception that doesn't match the exceptions we've seen. Looking at the code, it seems to catch "IOError()" which hash args[0] == errno. I'm not 100% sure why it is catching IOError rather than just SSHException. (I think paramiko used to raise multiple kinds of exceptions).

Anyway, we can fix our code to handle this error better, but fundamentally we are already in an error condition due to something else.