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

2018-10-12 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort commented on  JENKINS-53958  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline Jobs not started when locale master Node is offline   
 

  
 
 
 
 

 
 Daniel Hoerner 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.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2018-10-09 Thread daniel.hoer...@carefusion.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Hoerner created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53958  
 
 
  Pipeline Jobs not started when locale master Node is offline   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2018-10-09 11:25  
 
 
Environment: 
 Jenkins 2.145  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Daniel Hoerner  
 

  
 
 
 
 

 
 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.