Fixed! Thanks to Matt and Karsten :) On Fri, Jan 27, 2017 at 7:34 AM, Nigel Babu <[email protected]> wrote:
> Looks like a network issue in the cage or between the cage and rackspace. > I'll page people to get things going. I've filed > https://bugzilla.redhat.com/show_bug.cgi?id=1417020 > > On Fri, Jan 27, 2017 at 6:00 AM, Jeff Darcy <[email protected]> wrote: > >> I saw a bunch of jobs get aborted about half an hour ago, due to the >> nodes they were on going offline. I figured it was a power hit or >> something similar and things would come back by themselves, so I went off >> to dinner. Checking now, they're still offline and seeming inclined to >> remain so. I can ping, ssh port is open, but when I try to launch the >> slave agent Jenkins's ssh connection fails. >> >> [01/26/17 16:14:18] [SSH] Opening SSH connection to >> slave0.cloud.gluster.org:22. >> Connection timed out (Connection timed out) >> ERROR: Unexpected error in launching a slave. This is probably a bug in >> Jenkins. >> java.lang.IllegalStateException: Connection is not established! >> at com.trilead.ssh2.Connection.getRemainingAuthMethods(Connecti >> on.java:1030) >> at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSH >> PasswordAuthenticator.canAuthenticate(TrileadSSHPass >> wordAuthenticator.java:82) >> at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticato >> r.newInstance(SSHAuthenticator.java:207) >> at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticato >> r.newInstance(SSHAuthenticator.java:169) >> at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLaunc >> her.java:1212) >> at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher. >> java:711) >> at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher. >> java:706) >> at java.util.concurrent.FutureTask.run(FutureTask.java:262) >> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool >> Executor.java:1145) >> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo >> lExecutor.java:615) >> at java.lang.Thread.run(Thread.java:745) >> [01/26/17 16:15:21] Launch failed - cleaning up connection >> [01/26/17 16:15:21] [SSH] Connection closed. >> >> So, basically, it looks like no tests are going to happen until some >> manual intervention (beyond my own ability) occurs. >> _______________________________________________ >> Gluster-infra mailing list >> [email protected] >> http://lists.gluster.org/mailman/listinfo/gluster-infra >> > > > > -- > nigelb > -- nigelb
_______________________________________________ Gluster-infra mailing list [email protected] http://lists.gluster.org/mailman/listinfo/gluster-infra
