Sebastien Tardif created JENKINS-13237:
------------------------------------------
Summary: Unsuccessful SSH slave start do not timeout and cannot be
retry, even manually
Key: JENKINS-13237
URL: https://issues.jenkins-ci.org/browse/JENKINS-13237
Project: Jenkins
Issue Type: Bug
Components: ssh-slaves
Affects Versions: current
Environment: Windows 2008 to Oracle Linux (Redhat enterprise 5)
Reporter: Sebastien Tardif
Assignee: Kohsuke Kawaguchi
We have like 10 slaves. Too often one of the slave do not start on first
attempt using SSH configuration. The attempt never timeout, and we are then
stuck. There is no way to "kill" the attempt and retry. We end-up to use the
following workaround -> We create a new node, copying exactly the same
configuration, then it can connect!
An automatic "retry", adding timeout , and kill support will be useful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
