Since we moved to a NFS filesystem, sometimes (apparently) random jobs hang after the message below, before doing anything else.

Report Zero 142 log:

"Started by timer

[Pipeline] node

Running on Jenkins in /var/jenkins_home/.jenkins/workspace/Report Zero"

When failing, the job seems to be locked on some resource, but all the other jobs (except the one locked) proceed without issue, even if started (nearly) at the same time.

I attached the master's thread dump, system properties and the plugin list.

It seems it was hanging on the section below when I extracted the ThreadDump:

"jenkins.util.Timer 10" Id=142 Group=main TIMED_WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@52cafa24
at sun.misc.Unsafe.park(Native Method)

waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@52cafa24
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

PS: I don't know if moving to NFS caused the issue, but it is the main difference in the last few weeks.