Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Groovy script failed

Description

Hi, I had an ovirt-node-ng build failure and didn't get logs about what
happened due to:

Groovy script failed:

java.lang.NullPointerException: Cannot invoke method child() on null object

Failed job is
http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x86_64/279/
CAn you please check what happened?

–

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

Activity

Show:

Barak Korren November 5, 2017 at 9:22 AM

Maybe I did not explain things clearly. The exception you see in the groovy code is the result of the execution slave not being available any more by the time the Groovy code runs. It seem that something that the job was doing caused the slave to lose network connectivity with Jenkins. That is the kind of exception we cannot really anticipate of handle properly.

The groovy exception is not the reason behind longs not being available, the slave not being available to pull logs from is...

In any case the failing run was not kept, so we cannot debug further. Next time please mark it to be kept forever and set the description to clearly link to the relevant Jira ticket.

Closing this ticket with CANNOT-REPRODUCE. Please re-open if the issue re-occurs.

Sandro Bonazzola November 3, 2017 at 10:30 AM

Last failure I seen in that job is on September 18th but this bug is not really about the job failures reason, it is about the data collection after the failure, causing NPE in groovy script.
I would expect Exception is handled correctly and possibly avoided. Looks like a bug in the groovy script.

Eyal Edri October 31, 2017 at 2:33 PM

do you still see this error? it might have a problem only on that specific VM

Dafna Ron September 19, 2017 at 1:43 PM

All 3 failed tasks ran on the same vm.
I marked the vm as offline: vm0090.workers-phx.ovirt.org
and the reason for offline is the failed job: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x86_64/279/

Barak Korren September 19, 2017 at 12:51 PM

That failure is just a post-build Groovy script that expects some files to be accessible in the job workspace. The real issues seems to be a few lines before:

12:02:09 mount: /dev/loop2 is write-protected, mounting read-only 12:02:10 WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. 12:02:10 12:02:10 Starting install... 12:02:10 Retrieving file vmlinuz... | 5.6 MB 00:00 12:02:11 Retrieving file initrd.img... | 46 MB 00:00 12:02:11 Allocating 'diskGJ7pWv.img' | 5.0 GB 00:00 12:02:12 Domain installation still in progress. You can reconnect to 12:02:12 the console to complete the installation process. 12:35:12 ......................................................................................................................................................................................................FATAL: command execution failed 12:35:12 hudson.remoting.ProxyException: java.util.concurrent.TimeoutException: Ping started at 1505824272773 hasn't completed by 1505824512775 12:35:12 Caused: Command close created at 12:35:12 at hudson.remoting.Command.<init>(Command.java:60) 12:35:12 at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:1123) 12:35:12 at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:1121) 12:35:12 at hudson.remoting.Channel.close(Channel.java:1281) 12:35:12 at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:180) 12:35:12 at hudson.remoting.PingThread.ping(PingThread.java:130) 12:35:12 at hudson.remoting.PingThread.run(PingThread.java:86) 12:35:12 Caused: hudson.remoting.Channel$OrderlyShutdown: hudson.remoting.ProxyException: java.util.concurrent.TimeoutException: Ping started at 1505824272773 hasn't completed by 1505824512775 12:35:12 at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1129) 12:35:12 at hudson.remoting.Channel$1.handle(Channel.java:527) 12:35:12 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:83) 12:35:12 Caused: java.io.IOException: Backing channel 'vm0090.workers-phx.ovirt.org' is disconnected. 12:35:12 at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:192) 12:35:12 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:257) 12:35:12 at com.sun.proxy.$Proxy89.isAlive(Unknown Source) 12:35:12 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1043) 12:35:12 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1035) 12:35:12 at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155) 12:35:12 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109) 12:35:12 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) 12:35:12 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 12:35:12 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:735) 12:35:12 at hudson.model.Build$BuildExecution.build(Build.java:206) 12:35:12 at hudson.model.Build$BuildExecution.doRun(Build.java:163) 12:35:12 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:490) 12:35:12 at hudson.model.Run.execute(Run.java:1735) 12:35:12 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 12:35:12 at hudson.model.ResourceController.execute(ResourceController.java:97) 12:35:12 at hudson.model.Executor.run(Executor.java:405) 12:35:12 Build step 'Execute shell' marked build as failure 12:35:12 FATAL: channel is already closed 12:35:12 hudson.remoting.ProxyException: java.util.concurrent.TimeoutException: Ping started at 1505824272773 hasn't completed by 1505824512775 12:35:13 Caused: Command close created at 12:35:13 at hudson.remoting.Command.<init>(Command.java:60) 12:35:13 at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:1123) 12:35:13 at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:1121) 12:35:13 at hudson.remoting.Channel.close(Channel.java:1281) 12:35:13 at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:180) 12:35:13 at hudson.remoting.PingThread.ping(PingThread.java:130) 12:35:13 at hudson.remoting.PingThread.run(PingThread.java:86) 12:35:13 Caused: hudson.remoting.Channel$OrderlyShutdown: hudson.remoting.ProxyException: java.util.concurrent.TimeoutException: Ping started at 1505824272773 hasn't completed by 1505824512775 12:35:13 at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1129) 12:35:13 at hudson.remoting.Channel$1.handle(Channel.java:527) 12:35:13 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:83) 12:35:13 Caused: hudson.remoting.ChannelClosedException: channel is already closed 12:35:13 at hudson.remoting.Channel.send(Channel.java:605) 12:35:13 at hudson.remoting.Request.call(Request.java:130) 12:35:13 at hudson.remoting.Channel.call(Channel.java:829) 12:35:13 at hudson.Launcher$RemoteLauncher.launch(Launcher.java:959) 12:35:13 at hudson.Launcher$ProcStarter.start(Launcher.java:384) 12:35:13 at com.cloudbees.jenkins.plugins.sshagent.exec.ExecRemoteAgent.stop(ExecRemoteAgent.java:126) 12:35:13 at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.tearDown(SSHAgentBuildWrapper.java:417) 12:35:13 at hudson.model.Build$BuildExecution.doRun(Build.java:174) 12:35:13 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:490) 12:35:13 at hudson.model.Run.execute(Run.java:1735) 12:35:13 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 12:35:13 at hudson.model.ResourceController.execute(ResourceController.java:97) 12:35:13 at hudson.model.Executor.run(Executor.java:405)

Looks like Jenkins is timing out while trying to talk to the slave. But this may be caused by the error seen in the actual VM build process.

Cannot Reproduce

Details

Assignee

Reporter

Priority

Created September 19, 2017 at 12:42 PM
Updated December 4, 2017 at 3:44 PM
Resolved November 5, 2017 at 9:22 AM

Flag notifications