• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: jobgenerator-plugin
• Labels:

  • built-in-node-migration-regression
• Environment:

  Linux 3.10.0-1160.59.1.el7.x86_64 #1 SMP Wed Feb 23 16:47:03 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
  
  Jenkins 2.332.1
  
  Job Generator Version 1.22

[JENKINS-68140] built-in-node-migration-regression There are no nodes with the label 'master'

jenkins upv created issue - 2022-03-28 12:28

jenkins upv made changes - 2022-03-28 12:29

Description

Original: After applying the built-in-node-migration described in [https://www.jenkins.io/doc/book/managing/built-in-node-migration/] jenkins jobs of type Job Generator do not execute. The are pending for execution with the message  |(pending—There are no nodes with the label '[master|http://prejenkins.upv.es:8009/label/master]')| If I add the label master to the built-in node configuration, the jenkins jobs of type Job Generator do not execute but the message changes to:   |(pending—There are no nodes with the label '[master|http://prejenkins.upv.es:8009/label/master]')|

New: After applying the built-in-node-migration described in [https://www.jenkins.io/doc/book/managing/built-in-node-migration/] jenkins jobs of type Job Generator do not execute. The are pending for execution with the message  |(pending—There are no nodes with the label '[master|http://prejenkins.upv.es:8009/label/master]')| If I add the label master to the built-in node configuration, the jenkins jobs of type Job Generator do not execute but the message changes to:   |(pending—Waiting for next available executor on ‘builtin’)|

jenkins upv made changes - 2022-03-28 12:31

Description

Original: After applying the built-in-node-migration described in [https://www.jenkins.io/doc/book/managing/built-in-node-migration/] jenkins jobs of type Job Generator do not execute. The are pending for execution with the message  |(pending—There are no nodes with the label '[master|http://prejenkins.upv.es:8009/label/master]')| If I add the label master to the built-in node configuration, the jenkins jobs of type Job Generator do not execute but the message changes to:   |(pending—Waiting for next available executor on ‘builtin’)|

New: After applying the built-in-node-migration described in [https://www.jenkins.io/doc/book/managing/built-in-node-migration/] jenkins jobs of type Job Generator do not execute. The are pending for execution with the message  |(pending—There are no nodes with the label '[master|http://prejenkins.upv.es:8009/label/master]')| If I add the label master to the built-in node configuration, the jenkins jobs of type Job Generator do not execute but the message changes to:   |(pending—Waiting for next available executor on ‘builtin’)| even if there are free executors available, the jobs are always pending and do not execute

Collapse comment: Mark Waite added a comment - 2022-03-28 16:13, Edited by Mark Waite - 2022-04-19 11:57

Mark Waite added a comment - 2022-03-28 16:13 - edited

Job generator plugin was last released 8 years ago. The last commit to the repository was also 8 years ago. Probably best to convert your jobs to use Jenkins Pipeline.

If the plugin is crucial to you, you could adopt the plugin, modify it to support the current Jenkins versions, and release a new version. The "Contributing to Open Source" workshop may be helpful, including the 5 part video series.

The plugin also contains a known security vulnerability. Really best to convert your jobs to use Jenkins Pipeline.

Expand comment: Mark Waite added a comment - 2022-03-28 16:13, Edited by Mark Waite - 2022-04-19 11:57

Mark Waite added a comment - 2022-03-28 16:13 - edited Job generator plugin was last released 8 years ago. The last commit to the repository was also 8 years ago. Probably best to convert your jobs to use Jenkins Pipeline. If the plugin is crucial to you, you could adopt the plugin, modify it to support the current Jenkins versions, and release a new version. The "Contributing to Open Source" workshop may be helpful, including the 5 part video series. The plugin also contains a known security vulnerability. Really best to convert your jobs to use Jenkins Pipeline.

Mark Waite made changes - 2022-03-28 16:16

Summary

Original: built-in-node-migration-regression There are no nodes with the label 'master')

New: built-in-node-migration-regression There are no nodes with the label 'master'

Collapse comment: Eric Boehm added a comment - 2022-07-20 12:45

Eric Boehm added a comment - 2022-07-20 12:45

FWIW, I found a workaround to this problem. I created a node called 'master' on the Jenkins master.

Generator jobs now work without updating the plugin. It appears the plugin really wants the node name to be 'master' and the label 'master' isn't quite enough.
I have not explored the plugin to see why this occurs.

You may need to adjust the number of executors in 'Built-in Node' and 'master' since you now have two nodes on the same machine.

Expand comment: Eric Boehm added a comment - 2022-07-20 12:45

Eric Boehm added a comment - 2022-07-20 12:45 FWIW, I found a workaround to this problem. I created a node called 'master' on the Jenkins master. Generator jobs now work without updating the plugin. It appears the plugin really wants the node name to be 'master' and the label 'master' isn't quite enough. I have not explored the plugin to see why this occurs. You may need to adjust the number of executors in 'Built-in Node' and 'master' since you now have two nodes on the same machine.