[JIRA] [ssh-slaves] (JENKINS-17839) 1.514 breaks SSH nodes
stephane Buisson commented on JENKINS-17839 1.514 breaks SSH nodes Ok updated latest version of ssh slave plugin + manage credential plugin seems to work fin now This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17839) 1.514 breaks SSH nodes
stephane Buisson commented on JENKINS-17839 1.514 breaks SSH nodes Same problem in 1.524. What is the workaround, we ares stucked with this ? Thanks all This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17839) 1.514 breaks SSH nodes
Joern Huxhorn reopened JENKINS-17839 1.514 breaks SSH nodes Has this really been "fixed"? We just stumbled over the same issue. '~/.ssh' worked in prior versions but doesn't with 1.523. Now the file must be specified with an absolute path. This is less than ideal and finding the root of this issue took us nearly a whole workday. Change By: Joern Huxhorn (23/Jul/13 3:37 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17839) 1.514 breaks SSH nodes
bootstraponline closed JENKINS-17839 as Fixed 1.514 breaks SSH nodes Change By: bootstraponline (02/May/13 5:19 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17839) 1.514 breaks SSH nodes
bootstraponline resolved JENKINS-17839 as Fixed 1.514 breaks SSH nodes I set an absolute path to the file using "From a file on Jenkins master" and updated the username. Now it works again. Change By: bootstraponline (02/May/13 5:14 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17839) 1.514 breaks SSH nodes
sogabe commented on JENKINS-17839 1.514 breaks SSH nodes Caused by: java.io.IOException: Invalid PEM structure, '-BEGIN...' missing Your private key specified in Manage Credentials seems to be invalid. check it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17839) 1.514 breaks SSH nodes
bootstraponline created JENKINS-17839 1.514 breaks SSH nodes Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ssh-slaves Created: 02/May/13 3:38 PM Description: I updated Jenkins to 1.514 using Jenkins SSH Slaves plugin 0.25 and all the connected nodes error with: [05/02/13 11:26:09] [SSH] Opening SSH connection to x:22. ERROR: Failed to authenticate as x with credential=x-x-x-x-x java.io.IOException: Publickey authentication failed. at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:264) at com.trilead.ssh2.Connection.authenticateWithPublicKey(Connection.java:445) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.doAuthenticate(TrileadSSHPublicKeyAuthenticator.java:92) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:262) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:282) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:918) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:479) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:223) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: java.io.IOException: Invalid PEM structure, '-BEGIN...' missing at com.trilead.ssh2.crypto.PEMDecoder.parsePEM(PEMDecoder.java:138) at com.trilead.ssh2.crypto.PEMDecoder.decode(PEMDecoder.java:313) at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:173) ... 12 more [05/02/13 11:26:09] [SSH] Authentication failed. hudson.AbortException: Authentication failed. at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:923) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:479) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:223) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) [05/02/13 11:26:09] [SSH] Connection closed. The keys haven't changed and they worked fine before the upgrade... Environment: Ubuntu Project: Jenkins Priority: Major Reporter: bootstraponline This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
