When a Pipeline is triggered while the master node has been put temporarily offline, a OneOff (flyweight) executor is leaked.
As I'm unsure whether the issue lies in core or in the pipelines at put both components.
- Version: 2.121.3
Steps to reproduce
- Create a simple Pipeline Job, eg:
sh 'echo hello'
- Put the master node temporary offline
- Trigger the Pipeline build
- Put the master node back online
- Observe the leaked executor
This executor has the following characteristics:
Likely Stuck? false
Current Work Unit? null
Causes Of Interruption? 
Idle Start Milliseconds? 1534847122799
Asynchronous Execution: null
Jenkins logs show:
Executor #-1 for master grabbed hudson.model.queue.WorkUnit@4891a81f[work=hello] from queue but master went off-line before the task's worker thread started. No termination trace available.
Pipeline logs show nothing:
Démarré par l'utilisateur admin
Running in Durability level: MAX_SURVIVABILITY
Running on Jenkins in /Users/pierrebeitz/cbsupporthome/jenkins-home/workspace/hello
[hello] Running shell script
+ echo hello
[Pipeline] // node
[Pipeline] End of Pipeline
A restart of Jenkins will cleanup the executors.