[Gluster-infra] [Gluster-devel] NetBSD regressions not being triggered for patches

Niels de Vos ndevos at redhat.com
Thu Jun 11 10:51:52 UTC 2015


On Thu, Jun 11, 2015 at 09:48:22AM +0000, Emmanuel Dreyfus wrote:
> On Thu, Jun 11, 2015 at 07:26:00AM +0000, Emmanuel Dreyfus wrote:
> > In my opinion the fix to this problem is to start new VM. I was busy 
> > on other fronts hence I did not watched the situation, but it is still
> > grim, with most NetBSD slaves been in screwed state. We need to spin 
> > more.
> 
> Launching the slave on the new VM fails, but for once we have a 
> maningful error: either DNS names are duplicated, or jenkins has a bug.

There were some Jenkins slaves that all connected to
nbslave71.cloud.gluster.org. I thought I disabled all of those, and only
kept the Jenkins slave nbslave71.cloud.gluster.org enabled. Maybe I
missed a wrongly configured Jenkins slave and there are still more
Jenkins slaves using the single nbslave71.cloud.gluster.org VM?

I've just checked the online NetBSD slaves again, but they seem to have
been configured correctly... Maybe we are hitting a Jenkins bug, or
there was a (temporary?) issue with DNS resolution?

Niels

> 
> <===[JENKINS REMOTING CAPACITY]===>ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins.
> java.lang.IllegalStateException: Already connected
> 	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:466)
> 	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:371)
> 	at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:945)
> 	at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:133)
> 	at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:711)
> 	at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696)
> 	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:1145)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 	at java.lang.Thread.run(Thread.java:722)
> [06/11/15 02:37:46] Launch failed - cleaning up connection
> [06/11/15 02:37:46] [SSH] Connection closed.
> 
> 
> -- 
> Emmanuel Dreyfus
> manu at netbsd.org
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel


More information about the Gluster-infra mailing list