<div dir="ltr">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 <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1417020">https://bugzilla.redhat.com/show_bug.cgi?id=1417020</a><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 27, 2017 at 6:00 AM, Jeff Darcy <span dir="ltr"><<a href="mailto:jdarcy@redhat.com" target="_blank">jdarcy@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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.<br>
<br>
[01/26/17 16:14:18] [SSH] Opening SSH connection to <a href="http://slave0.cloud.gluster.org:22" rel="noreferrer" target="_blank">slave0.cloud.gluster.org:22</a>.<br>
Connection timed out (Connection timed out)<br>
ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins.<br>
java.lang.<wbr>IllegalStateException: Connection is not established!<br>
at com.trilead.ssh2.Connection.<wbr>getRemainingAuthMethods(<wbr>Connection.java:1030)<br>
at com.cloudbees.jenkins.plugins.<wbr>sshcredentials.impl.<wbr>TrileadSSHPasswordAuthenticato<wbr>r.canAuthenticate(<wbr>TrileadSSHPasswordAuthenticato<wbr>r.java:82)<br>
at com.cloudbees.jenkins.plugins.<wbr>sshcredentials.<wbr>SSHAuthenticator.newInstance(<wbr>SSHAuthenticator.java:207)<br>
at com.cloudbees.jenkins.plugins.<wbr>sshcredentials.<wbr>SSHAuthenticator.newInstance(<wbr>SSHAuthenticator.java:169)<br>
at hudson.plugins.sshslaves.<wbr>SSHLauncher.openConnection(<wbr>SSHLauncher.java:1212)<br>
at hudson.plugins.sshslaves.<wbr>SSHLauncher$2.call(<wbr>SSHLauncher.java:711)<br>
at hudson.plugins.sshslaves.<wbr>SSHLauncher$2.call(<wbr>SSHLauncher.java:706)<br>
at java.util.concurrent.<wbr>FutureTask.run(FutureTask.<wbr>java:262)<br>
at java.util.concurrent.<wbr>ThreadPoolExecutor.runWorker(<wbr>ThreadPoolExecutor.java:1145)<br>
at java.util.concurrent.<wbr>ThreadPoolExecutor$Worker.run(<wbr>ThreadPoolExecutor.java:615)<br>
at java.lang.Thread.run(Thread.<wbr>java:745)<br>
[01/26/17 16:15:21] Launch failed - cleaning up connection<br>
[01/26/17 16:15:21] [SSH] Connection closed.<br>
<br>
So, basically, it looks like no tests are going to happen until some manual intervention (beyond my own ability) occurs.<br>
______________________________<wbr>_________________<br>
Gluster-infra mailing list<br>
<a href="mailto:Gluster-infra@gluster.org">Gluster-infra@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-infra" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-infra</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">nigelb<br></div></div>
</div>