- changed status to resolved
ServerJob should contain result when unable to establish ssh connection
Issue #9
resolved
ServerJob objects that are unable to establish an ssh connection have a status of 255 but the results is blank. We should return 'Unable to establish ssh connection' as a result as well as a status code of 255.
{'posthook': None, 'results': [], 'name': 'host.example.com', 'combine_output': True, 'key': '/Users/jdoe/.ssh/id_rsa', 'username': 'jdoe', '_conn': None, 'sshtimeout': 300, 'password': None, 'cmdtimeout': 300, 'prehook': None, 'debuglevel': 0, 'status': 255, 'runlocal': False, 'cmds': ["sysctl -a"]}
Comments (2)
-
reporter -
reporter - removed version
Removing version: v3.0 (automated comment)
- Log in to comment
Now capturing SSH connection error and returning it as result[0]. Commit: 7f2e79b