• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: core, ssh-credentials-plugin
• Labels:

  None
• Environment:

  Jenkins ver 2.163
  Linux
  Chrome

[JENKINS-55971] SSH Host key matches, Authentication failed, Slaves failed to reconnect

Steve Graham created issue - 2019-02-05 09:11

Steve Graham made changes - 2019-02-05 09:15

Description

Original: SSHLauncher\{host='myhost', port=22, credentialsId='aaa-bbb-ccc-myRealCredentials', jvmOptions='', javaPath='/home/bla/jenkins/bin/java', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.ManuallyTrustedKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true} [02/04/19 22:09:16] [SSH] Opening SSH connection to ligenr10.swb.siemens.de:22. [02/04/19 22:09:16] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed. [02/04/19 22:09:16] [SSH] {color:#FF0000}Authentication failed.{color} Manage old data complained on startup - ( didn't take real notice of message ) Credentials, private key, was corrupted when starting Jenkins after updating to 2.163 Eventually found and corrected.

New: SSHLauncher\{host='myhost', port=22, credentialsId='aaa-bbb-ccc-myRealCredentials', jvmOptions='', javaPath='/home/bla/jenkins/bin/java', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.ManuallyTrustedKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}  [02/04/19 22:09:16] [SSH] Opening SSH connection to ligenr10.swb.siemens.de:22.  [02/04/19 22:09:16] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed.  [02/04/19 22:09:16] [SSH] {color:#ff0000}Authentication failed.{color} Manage old data complained on startup - ( didn't take real notice of message ) Credentials, private key, was corrupted when starting Jenkins after updating to 2.163 Eventually found and corrected. Might not be a bug but user error. However, caused 8 hour loss of Jenkins until problem found.

Steve Graham made changes - 2019-02-05 09:25

Description

Original: SSHLauncher\{host='myhost', port=22, credentialsId='aaa-bbb-ccc-myRealCredentials', jvmOptions='', javaPath='/home/bla/jenkins/bin/java', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.ManuallyTrustedKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}  [02/04/19 22:09:16] [SSH] Opening SSH connection to ligenr10.swb.siemens.de:22.  [02/04/19 22:09:16] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed.  [02/04/19 22:09:16] [SSH] {color:#ff0000}Authentication failed.{color} Manage old data complained on startup - ( didn't take real notice of message ) Credentials, private key, was corrupted when starting Jenkins after updating to 2.163 Eventually found and corrected. Might not be a bug but user error. However, caused 8 hour loss of Jenkins until problem found.

New: SSHLauncher\{host='myhost', port=22, credentialsId='aaa-bbb-ccc-myRealCredentials', jvmOptions='', javaPath='/home/bla/jenkins/bin/java', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.ManuallyTrustedKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}  [02/04/19 22:09:16] [SSH] Opening SSH connection to ligenr10.swb.siemens.de:22.  [02/04/19 22:09:16] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed.  [02/04/19 22:09:16] [SSH] {color:#ff0000}Authentication failed.{color} Manage old data complained on startup - ( didn't take real notice of message ) Credentials, private key, was corrupted when starting Jenkins after updating to 2.163 Eventually found and corrected. ( Jenkins- Credentials->System->Global Credentials -> name ) ( updated Private Key - entered directly ) Might not be a bug but user error. However, caused 8 hour loss of Jenkins until problem found.

Steve Graham made changes - 2019-02-05 09:26

Description

Original: SSHLauncher\{host='myhost', port=22, credentialsId='aaa-bbb-ccc-myRealCredentials', jvmOptions='', javaPath='/home/bla/jenkins/bin/java', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.ManuallyTrustedKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}  [02/04/19 22:09:16] [SSH] Opening SSH connection to ligenr10.swb.siemens.de:22.  [02/04/19 22:09:16] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed.  [02/04/19 22:09:16] [SSH] {color:#ff0000}Authentication failed.{color} Manage old data complained on startup - ( didn't take real notice of message ) Credentials, private key, was corrupted when starting Jenkins after updating to 2.163 Eventually found and corrected. ( Jenkins- Credentials->System->Global Credentials -> name ) ( updated Private Key - entered directly ) Might not be a bug but user error. However, caused 8 hour loss of Jenkins until problem found.

New: SSHLauncher\{host='myhost', port=22, credentialsId='aaa-bbb-ccc-myRealCredentials', jvmOptions='', javaPath='/home/bla/jenkins/bin/java', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.ManuallyTrustedKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}  [02/04/19 22:09:16] [SSH] Opening SSH connection to ligenr10.swb.siemens.de:22.  [02/04/19 22:09:16] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed.  [02/04/19 22:09:16] [SSH] {color:#ff0000}Authentication failed.{color} Manage old data complained on startup - ( didn't take real notice of message ) Credentials, private key, was corrupted when starting Jenkins after updating to 2.163 *+Eventually found and resolved.+* ( Jenkins- Credentials->System->Global Credentials -> name ) ( updated Private Key - entered directly ) Might not be a bug but user error. However, caused 8 hour loss of Jenkins until problem found.

Devin Nusbaum made changes - 2019-02-05 14:09

Assignee

Original: Devin Nusbaum [ dnusbaum ]

Devin Nusbaum made changes - 2019-02-07 14:48

Link

New: This issue duplicates JENKINS-52232 [ JENKINS-52232 ]

Devin Nusbaum made changes - 2019-02-07 14:49

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

divya katike made changes - 2019-03-10 10:19

Resolution	Original: Duplicate [ 3 ]
Status	Original: Resolved [ 5 ]	New: In Review [ 10005 ]