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

Nodes not launched if another node with same label online, even if busy

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Jenkins 2.5

      Java Version "1.7.0_85"
      OpenJDK Runtime Environment (rhel-2.6.1.3.el6_7-x86_64 u85-b01)
      OpenJDK 64-Bit Server VM (build 24.85-b03, mixed mode)
    • Similar Issues:

      Description

      When given a label to the job (for example, machinegroup1) and a node matching that label is online but busy, Jenkins will very often not bring a node online to perform this job, instead saying "Waiting for next available executor" and waiting in the queue until the other job is done (sometimes days). If there is no online machine that matches the label, it brings one online properly.

      I watched the logs and it gets as far as attempting to map the job to a possible set of executors, then repeatedly fails until it determines that none are suitable candidates.

      Our nodes are launched on-demand, offline when not in use.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            Assignee:
            domi Dominik Bartholdi
            Reporter:
            s_browne Sam Browne
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: