Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42538

Build Flow jobs stuck waiting on next available executor when using label parameter to restrict job to vpshere slave


    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None

      Testing Jenkins upgrade from 2.7.2 to 2.32.2 with installed plugins upgraded as well.

      We use a lot of flow jobs and post upgrade they don't work when combined with a label parameter with a value that isn't 'master' i.e. we can't get a flow job to run on a slave using the label parameter.

      1. As per screen shots, create a simple flow job with a single Label parameter
      2. Build the job with the label value of master and it works.
      3. Rebuild the job using a label for a connected slave that has free executors, the job permanently sits in the Build Queue - 'Waiting for next available executor'
      4. Alternatively, change the job configuration to no longer have a parameter but select 'Restrict where this project can be run' and set the slave name. Rebuild the job and same issue - sits in Build Queue.
      5. With the job sat in the Build Queue I can submit a separate 'free style project' also configured with a Label parameter for the same slave name and it completes ok.

      During the upgrade steps neither if the two obvious plugins were upgraded:

      • Node and Label parameter plugin still at 1.7.2
      • Build Flow plugin still at 0.20

      The Node and Label  parameter had dependencies that were upgraded, but reverting both, and using the Jenkins auto restart option from the plugin page, does not solve the issue.

      • parameterized-trigger Upgraded from 2.32 to 2.33
      • token-macro Upgraded from 1.12.1 to 2.0

      I'm about to restart the entire upgrade process again to try to narrow down which change causes this, but any advice/thoughts would be appreciated.

            Unassigned Unassigned
            elliottjones Elliott Jones
            0 Vote for this issue
            2 Start watching this issue