Re: [Gluster-infra] [IMPORTANT!] Entire test cluster is down
> Fixed! Thanks to Matt and Karsten :) ...and yourself, of course. Thanks for the prompt response. ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] [IMPORTANT!] Entire test cluster is down
Fixed! Thanks to Matt and Karsten :) On Fri, Jan 27, 2017 at 7:34 AM, Nigel Babu 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 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 >> Gluster-infra@gluster.org >> http://lists.gluster.org/mailman/listinfo/gluster-infra >> > > > > -- > nigelb > -- nigelb ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1417020] Jenkins nodes in Rackspace offline
https://bugzilla.redhat.com/show_bug.cgi?id=1417020 Nigel Babu changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |CURRENTRELEASE Last Closed||2017-01-26 21:49:49 --- Comment #1 from Nigel Babu --- Paged Karsten and Matt. Matt fixed it up. Turns out it was a network configuration error. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=XBBUuM9wQy&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] [IMPORTANT!] Entire test cluster is down
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 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( > Connection.java:1030) > at com.cloudbees.jenkins.plugins.sshcredentials.impl. > TrileadSSHPasswordAuthenticator.canAuthenticate( > TrileadSSHPasswordAuthenticator.java:82) > at com.cloudbees.jenkins.plugins.sshcredentials. > SSHAuthenticator.newInstance(SSHAuthenticator.java:207) > at com.cloudbees.jenkins.plugins.sshcredentials. > SSHAuthenticator.newInstance(SSHAuthenticator.java:169) > at hudson.plugins.sshslaves.SSHLauncher.openConnection( > SSHLauncher.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( > ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.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 > Gluster-infra@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-infra > -- nigelb ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1417020] New: Jenkins nodes in Rackspace offline
https://bugzilla.redhat.com/show_bug.cgi?id=1417020 Bug ID: 1417020 Summary: Jenkins nodes in Rackspace offline Product: GlusterFS Version: mainline Component: project-infrastructure Assignee: b...@gluster.org Reporter: nig...@redhat.com CC: b...@gluster.org, gluster-infra@gluster.org We're having some network issues between the cage and Rackspace which is keeping the Jenkins nodes offline. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=MhXPSTos69&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [IMPORTANT!] Entire test cluster is down
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(Connection.java:1030) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPasswordAuthenticator.canAuthenticate(TrileadSSHPasswordAuthenticator.java:82) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:207) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:169) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.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(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.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 Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1416953] New: Request gerrit integration for gluster/ test github repository
https://bugzilla.redhat.com/show_bug.cgi?id=1416953 Bug ID: 1416953 Summary: Request gerrit integration for gluster/test github repository Product: GlusterFS Version: mainline Component: project-infrastructure Assignee: b...@gluster.org Reporter: srang...@redhat.com CC: b...@gluster.org, gluster-infra@gluster.org The repo https://github.com/gluster/test is a playground for our github move. We prototyped some project boards and labels there. Going further we want to prototype and see how github issues and its mentions in commits can be leveraged to make a move to github issues and stop using Bugzilla. Towards this, this is a request to be able to submit gerrit reviews against the test repository (possibly via our gerrit instance), so that we can play with and check how this can function. We want such a playground within our infra, so that in the gluster space other maintainers can also try out the workflow with ease and comment on the changes. The core need is, we should be able to add test as a project to our gerrit instance, and be able to open reviews and submit changes from there. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Y6l9i4AMYY&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra
