Ohai,
seems since the Jenkins upgrade yesterday, our node cannot execute the GitSCM plugin anymore.
java.lang.NoClassDefFoundError: Could not initialize class com.sun.proxy.$Proxy42 at sun.reflect.GeneratedConstructorAccessor580.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:739) at hudson.remoting.RemoteInvocationHandler.wrap(RemoteInvocationHandler.java:169) at hudson.remoting.Channel.export(Channel.java:813) at hudson.remoting.Channel.export(Channel.java:776) at org.jenkinsci.plugins.gitclient.LegacyCompatibleGitAPIImpl.writeReplace(LegacyCompatibleGitAPIImpl.java:204) at sun.reflect.GeneratedMethodAccessor7120.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:1244) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1136) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348) at hudson.remoting.UserRequest._serialize(UserRequest.java:263) at hudson.remoting.UserRequest.serialize(UserRequest.java:272) at hudson.remoting.UserRequest.perform(UserRequest.java:222) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:375) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:73) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:118) Caused: java.io.IOException: Remote call on JNLP4-connect connection from slave01.ci.centos.org/172.19.0.16:38434 failed at hudson.remoting.Channel.call(Channel.java:1007) at hudson.FilePath.act(FilePath.java:1158) at hudson.FilePath.act(FilePath.java:1147) at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:121) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:906) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:837) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1290) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:125) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
from https://ci.centos.org/job/foreman-pipeline-foreman-2.5-ubuntu1804-install/7/console
(feel free to re-run this job for testing!)
A simple echo job works (https://ci.centos.org/view/Foreman/job/foreman-ci-centos-simple-test/1841/console), so the node as such is connected properly.
From an outside perspective, I'd guess a plugin version missmatch or something?
the most trivial reproducer for this is:
pipeline { agent { label 'foreman' } stages { stage('Echo') { steps { git url: 'https://github.com/theforeman/forklift.git' } } } }
Metadata Update from @arrfab: - Issue assigned to siddharthvipul1 - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: centos-ci-infra, high-gain, low-trouble
arrfab has updated our agent (it was out of date) and things are working again.
I think other agents will be updated soon too.
just worked with @evgeni on IRC and we confirm that updating the agent (newer java.jar) and reconnect seems to be working. @evgeni : if you can just give positive feedback, I'll close this one
Metadata Update from @arrfab: - Issue assigned to arrfab (was: siddharthvipul1)
ACK, this is now resolved for us!
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.