-
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
[JENKINS-53958] Pipeline Jobs not started when locale master Node is offline
Environment | Original: Jenkins 2.145 | New: Jenkins 2.145; Jenkins 2.332.3 |
Link | New: This issue relates to JENKINS-53880 [ JENKINS-53880 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Remote Link | New: This issue links to "PR-9203 (Web Link)" [ 29638 ] |
dhoerner Not clear what you mean, what do you mean by "defined another master node" and "alternative master"?
Specifically what does this mean:
> I have defined another master Node with Name 'master' and this Node is online.