-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Jenkins 2.145; Jenkins 2.332.3
After updating Jenkins to 2.145, I'm not able to run any more pipeline jobs.
I have defined another master Node with Name 'master' and this Node is online.
I have took the original Master (the master Jenkins node) offline. When I try to start a pipeline job, the job is never started (also not displayed in execution list) and I can find following error in the log:
Executor #-1 for master grabbed hudson.model.queue.WorkUnit@10eeb25[work=PIPELINE NAME] from queue but master went off-line before the task's worker thread started. No termination trace available.
Before updating Jenkins, all works as expected and the jobs were started at the "alternative" master.
- relates to
-
JENKINS-53880 Build step trigger pipeline job hangs when master node set to zero executors
- Open
- links to