[JENKINS-53958] Pipeline Jobs not started when locale master Node is offline

[jenkins-infra-bot]

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.

 

---

Originally reported by dhoerner, imported from: Pipeline Jobs not started when locale master Node is offline

• status: Resolved
• priority: Critical
• component(s): pipeline
• resolution: Fixed
• resolved: 2024-05-12T10:05:12+00:00
• votes: 4
• watchers: 7
• imported: 2025-12-08

Raw content of original issue

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.
 

• environment: Jenkins 2.145; Jenkins 2.332.3

[jenkins-infra-bot]

• Remote link associated with this issue:

  • PR-9203

[jenkins-infra-bot]

svanoort:

• Original comment link
• Raw content of original comment:

  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.
  

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.

[jenkins-infra-bot]

enuotiz:

• Original comment link
• Raw content of original comment:

  I had (almost) the same warning that prevents me to create a pipeline using Jenkinsfile, and after turning the master node back online it worked...I don't know why it's related though...
  

I had (almost) the same warning that prevents me to create a pipeline using Jenkinsfile, and after turning the master node back online it worked...I don't know why it's related though...

[jenkins-infra-bot]

notmyfault:

• Original comment link
• Raw content of original comment:

  I experienced the same today on 2.339. If no agent is available, a pipeline job is removed from the queue, as opposed to other job types, which remain in the build queue until an agent is available. 
  

I experienced the same today on 2.339. If no agent is available, a pipeline job is removed from the queue, as opposed to other job types, which remain in the build queue until an agent is available. 

[jenkins-infra-bot]

masterxilo:

• Original comment link
• Raw content of original comment:

  Having the same issue on Jenkins 2.387.1
  
  The log shows
  
  Mar 22, 2023 10:11:03 PM WARNING hudson.model.Executor resetWorkUnitExecutor #-1 for Built-In Node grabbed hudson.model.queue.WorkUnit@7f3c6ce3[work=job-submission-protocol-simplified] from queue but Built-In Node went off-line before the task's worker thread started. No termination trace available. 
  
  whenever I try to submit a new job and the job simply disappears.
  

Having the same issue on Jenkins 2.387.1

The log shows

Mar 22, 2023 10:11:03 PM WARNING hudson.model.Executor resetWorkUnitExecutor #-1 for Built-In Node grabbed hudson.model.queue.WorkUnit@​7f3c6ce3[work=job-submission-protocol-simplified] from queue but Built-In Node went off-line before the task's worker thread started. No termination trace available. 

whenever I try to submit a new job and the job simply disappears.

[jenkins-infra-bot]

mawinter69:

• Original comment link
• Raw content of original comment:

  Can still be seen on current weekly 2.455
  

Can still be seen on current weekly 2.455