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

Sometimes after Jenkins restart platform labels are not available

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • platformlabeler-plugin
    • None
    • Jenkins 1.410 on Red Hat Enterprise Linux 5.5 x86_64, platformlabeler 1.1

      Sometimes after Jenkins restarts, jobs tied to specific label end up in queue indefinitely, marked as 'no node labeled ... available'.

      My situation is as follows: I have 4 nodes marked (by platformlabeler) as RedHatEnterpriseServer. When Jenkins gets up, it initiates a build for three jobs, they all end up in queue with this 'no node labeled 'RedHatEnterpriseServer' available'. However, if I check any of the nodes which should be marked with this label, they all do have their label applied. The only solution for this situation is to enter configuration for any of those nodes and press Save button. All labels are then suddenly available to Jenkins and the jobs get started on every proper node.

      I don't know if this is related to platformlabeler or the core itself, but it would be nice if somebody could look at it, as this behavior requires Jenkins monitoring to see whether this happens or not.

          [JENKINS-9586] Sometimes after Jenkins restart platform labels are not available

          evernat added a comment -

          Is it reproduced with a recent Jenkins version?

          evernat added a comment - Is it reproduced with a recent Jenkins version?

          It is. I just encountered it again yesterday starting up Jenkins 1.499.

          Krzysztof Malinowski added a comment - It is. I just encountered it again yesterday starting up Jenkins 1.499.

          Oleg Nenashev added a comment -

          Assigned the issue to the proper component.

          Oleg Nenashev added a comment - Assigned the issue to the proper component.

          Mark Waite added a comment - - edited

          I continue to see this with platform labeler plugin 5.4 on my Jenkins 2.204.1 installation

          Mark Waite added a comment - - edited I continue to see this with platform labeler plugin 5.4 on my Jenkins 2.204.1 installation

          Mark Waite added a comment -

          I still see this sometimes with platformlabeler 7.1 on Jenkins 2.249.1. Saving the configuration of any agent will cause the labels to appear on all the agents.

          Mark Waite added a comment - I still see this sometimes with platformlabeler 7.1 on Jenkins 2.249.1. Saving the configuration of any agent will cause the labels to appear on all the agents.

          Mark Waite added a comment -

          Mark Waite added a comment - May be resolved by JENKINS-72224 in https://github.com/jenkinsci/platformlabeler-plugin/releases/tag/2287.va_d728a_42d7f1

            Unassigned Unassigned
            raspy Krzysztof Malinowski
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: