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

Node.LabelMissing error in Jenkins 2.71


    • Similar Issues:


      Short problem description: Job on dedicated slave not started since Jenkins 2.71


      Detailed description:

      1. I have jobs that run only on slave nodes with dedicated labels (label-A && label-B).
      2. Then, I have slave nodes that contain these labels label-A, label-B, label-C, ... .
      3. In the slave node configuration, I have also configured that only a special user (user-ID coming from LDAP) is allowed to run jobs on this slave.
      4. Problem: when I want to launch the job, the job is queued with the hint Node.LabelMissing (I found it in Google: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/model/Messages_de.properties). When I move the mouse over the job in the queue, I get more details about the missing label. The list contains many many slave nodes which do not contain the label, which is correct. But it seems that my dedicated node is not considered at all.
      5. After rolling back to Jenkins 2.70 (exchanging the war file, no change in plugins), the job can be started without any problems.



          michaelmotteler Michael M. created issue -
          jglick Jesse Glick made changes -
          Field Original Value New Value
          Labels label node slave label node regression slave
          michaelmotteler Michael M. made changes -
          Attachment image-2017-08-16-07-12-43-062.png [ 39295 ]
          jglick Jesse Glick made changes -
          Component/s job-restrictions-plugin [ 18044 ]
          Labels label node regression slave label node regression slave user


            • Assignee:
              michaelmotteler Michael M.
            • Votes:
              0 Vote for this issue
              4 Start watching this issue


              • Created: