-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major
-
Component/s: ssh-credentials-plugin, ssh-slaves-plugin
-
None
-
Environment:Jenkins 1.138.3
ssh-slaves-plugin 1.29.1
Java 1.8.0_171-8u171
OS: Debian Stretch (Server and Jenkins Nodes)
-
ssh-slaves-1.29.2
Starting with ssh-slaves-plugin 1.29.1, the SSH agent connection with all nodes fail.
Logs on Jenkins (logfile):
[11/21/18 09:38:38] SSH Launch of HOSTNAME on HOSTNAME failed in 391 ms
Logs on Jenkins (UI):
SSHLauncher{host='HOSTNAME', port=22, credentialsId='b1f94972-dfce-45d0-9cb1-f14e3dc324b9', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.ManuallyTrustedKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}
[11/21/18 09:40:05] [SSH] Opening SSH connection to HOSTNAME:22.
[11/21/18 09:40:05] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed.
[11/21/18 09:40:05] [SSH] Authentication failed.
Authentication failed.
[11/21/18 09:40:05] Launch failed - cleaning up connection
[11/21/18 09:40:05] [SSH] Connection closed.
The auth.log of a node just contains:
Closed due to user request. [preauth]
Downgrading to 1.28.1 fixes the issue.
- duplicates
-
JENKINS-52232 Credentials not usable after upgrade to 1.14
-
- Reopened
-
- is related to
-
JENKINS-54884 ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working
-
- Resolved
-
-
JENKINS-52232 Credentials not usable after upgrade to 1.14
-
- Reopened
-
- links to