[JIRA] [ssh-slaves] (JENKINS-17366) ssh slave login via keyfile not working in 0.23
Kohsuke Kawaguchi commented on JENKINS-17366 ssh slave login via keyfile not working in 0.23 Joakim, are you sure 0.23 is working (as opposed to just not showing the stack trace?) Also see JENKINS-17648 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-17366) ssh slave login via keyfile not working in 0.23
Joakim Sandström commented on JENKINS-17366 ssh slave login via keyfile not working in 0.23 I downgraded from 0.24 to 0.23 and now it works 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-17366) ssh slave login via keyfile not working in 0.23
Joakim Sandström edited a comment on JENKINS-17366 ssh slave login via keyfile not working in 0.23 Using Jenkins 1.511 and slave-plugin 0.24. SSH public key authentication without passphrase. [04/17/13 08:18:57] [SSH] Opening SSH connection to limetti.x:22. ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. hudson.security.AccessDeniedException2: anonymous is missing the Administer permission at hudson.security.ACL.checkPermission(ACL.java:54) at hudson.model.Node.checkPermission(Node.java:394) at com.cloudbees.plugins.credentials.SystemCredentialsProvider.save(SystemCredentialsProvider.java:178) at hudson.plugins.sshslaves.SSHLauncher.upgrade(SSHLauncher.java:407) at hudson.plugins.sshslaves.SSHLauncher.getCredentials(SSHLauncher.java:351) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:907) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:473) 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:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) [04/17/13 08:18:57] [SSH] Connection 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-17366) ssh slave login via keyfile not working in 0.23
Joakim Sandström commented on JENKINS-17366 ssh slave login via keyfile not working in 0.23 SSH public key authentication without passphrase. [04/17/13 08:18:57] [SSH] Opening SSH connection to limetti.x:22. ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. hudson.security.AccessDeniedException2: anonymous is missing the Administer permission at hudson.security.ACL.checkPermission(ACL.java:54) at hudson.model.Node.checkPermission(Node.java:394) at com.cloudbees.plugins.credentials.SystemCredentialsProvider.save(SystemCredentialsProvider.java:178) at hudson.plugins.sshslaves.SSHLauncher.upgrade(SSHLauncher.java:407) at hudson.plugins.sshslaves.SSHLauncher.getCredentials(SSHLauncher.java:351) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:907) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:473) 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:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) [04/17/13 08:18:57] [SSH] Connection 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-17366) ssh slave login via keyfile not working in 0.23
Kohsuke Kawaguchi started work on JENKINS-17366 ssh slave login via keyfile not working in 0.23 Change By: Kohsuke Kawaguchi (16/Apr/13 1:52 AM) Status: Open In Progress 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-17366) ssh slave login via keyfile not working in 0.23
Kohsuke Kawaguchi commented on JENKINS-17366 ssh slave login via keyfile not working in 0.23 I've released 0.24 with improved error diagnostics. If you are seeing this problem, please upgrade to ssh-slaves 0.24 and report the error message in the slave log that you see. Also, as we still haven't quite determined the root cause yet, please report the type of the authentication method you use (username+password? private key? if so, with or without passphrase? do you specify the user name?) Thanks for your cooperation! 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-17366) ssh slave login via keyfile not working in 0.23
Kohsuke Kawaguchi commented on JENKINS-17366 ssh slave login via keyfile not working in 0.23 I've been trying the upgrade scenario today, and so far I have been unable to reproduce this problem. I created a passphrase-protected private key and used Jenkins 1.480 (with ssh-slaves plugin 0.22) to set up a slave. The slave also uses a different user name than what the master runs. I then upgraded to Jenkins 1.511, which uses the ssh-slaves plugin 0.23, and I see that the configuration has been successfully migrated, and the slave connected as it should be. So there must be something deeper going on that what it appears. I do agree with the poor error message. I have just fixed this. This would let us better understand what's going wrong. This error message fix will be in 0.24. 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-17366) ssh slave login via keyfile not working in 0.23
Yves Schumann commented on JENKINS-17366 ssh slave login via keyfile not working in 0.23 Same here. Interaction with credential plugin seems to be wrong/broken. Rollback to 0.22 solved the problem. 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-17366) ssh slave login via keyfile not working in 0.23
Stephen Morrison commented on JENKINS-17366 ssh slave login via keyfile not working in 0.23 I'm seeing something similar, where when I select the correct credential with the right username it works, but when I come back later the credential in the slave config has mysteriously changed to be the user of the Master and Jenkins can no longer log into the slave. 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-17366) ssh slave login via keyfile not working in 0.23
Hajime Fujita commented on JENKINS-17366 ssh slave login via keyfile not working in 0.23 I had a similar problem in my environment, where the master and the slave nodes use different username for jenkins. Say, "masteruser" for the master node and "slaveuser" for the slave. When login failed for the slave, Jenkins tried to connect to the slave node with "masteruser", according to the log file in the slave node (/var/log/auth.log, since it's Ubuntu-based host). When this happened, I came back to the slave node configuration page (Manage Jenkins -> Manage Nodes -> (particular slave node) -> Configure). There were multiple credentials in "Launch Method - Credentials" drop down list. I could see four items, saying: slaveuser (slavehostname) masteruser (slavehostname) slaveuser (slavehostname) masteruser (slavehostname) Clearly something weird was going on there (duplicated entries). Anyway, I selected the third one for some reason (second and fourth are definitely the wrong ones), then it suddenly worked. 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.
