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

Executors dead due to parenthesis in node name

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • core
    • None
    • Apache Software Foundation Hudson installation. Master 1.372 on Ubuntu. Slaves on Windows, Solaris and Ubuntu all affected.

      All our executors dies with the following stacktrace. We have a slave named "lucene.zones.apache.org (Solaris 10)", unknown if any job has assigned this as a label.

      java.lang.IllegalArgumentException: Invalid label expression: lucene.zones.apache.org (Solaris 10)
      at hudson.model.Hudson.getLabel(Hudson.java:1381)
      at hudson.model.AbstractProject.getAssignedLabel(AbstractProject.java:288)
      at hudson.model.Node.canTake(Node.java:242)
      at hudson.model.Queue$JobOffer.canTake(Queue.java:190)
      at hudson.model.Queue$ApplicableJobOfferList.(Queue.java:818)
      at hudson.model.Queue$ApplicableJobOfferList.(Queue.java:810)
      at hudson.model.Queue.pop(Queue.java:740)
      at hudson.model.Executor.grabJob(Executor.java:165)
      at hudson.model.Executor.run(Executor.java:106)
      Caused by: line 1:25: unexpected token: (
      at hudson.model.label.LabelExpressionParser.term4(LabelExpressionParser.java:170)
      at hudson.model.label.LabelExpressionParser.term3(LabelExpressionParser.java:119)
      at hudson.model.label.LabelExpressionParser.term2(LabelExpressionParser.java:89)
      at hudson.model.label.LabelExpressionParser.term1(LabelExpressionParser.java:60)
      at hudson.model.label.LabelExpressionParser.expr(LabelExpressionParser.java:50)
      at hudson.model.Label.parseExpression(Label.java:458)
      at hudson.model.Hudson.getLabel(Hudson.java:1379)
      ... 8 more

          [JENKINS-7222] Executors dead due to parenthesis in node name

          protocol7b created issue -

          protocol7b added a comment -

          Further investigation showed that we did indeed have a job that was tied to the the label name "lucene.zones.apache.org (Solaris 10)". This job was in the build queue when this happened. Fixing that and restarting our master resurrected the slaves. However, it seems a bit brutal to kill the executor threads due to this problem

          protocol7b added a comment - Further investigation showed that we did indeed have a job that was tied to the the label name "lucene.zones.apache.org (Solaris 10)". This job was in the build queue when this happened. Fixing that and restarting our master resurrected the slaves. However, it seems a bit brutal to kill the executor threads due to this problem

          protocol7b added a comment -

          I'm guessing this is due to the label configuration now taking a boolean expression. Most of our slaves have names containing parenthesis, which brakes in 1.372. Are node names containing parenthesis not allowed?

          protocol7b added a comment - I'm guessing this is due to the label configuration now taking a boolean expression. Most of our slaves have names containing parenthesis, which brakes in 1.372. Are node names containing parenthesis not allowed?
          Jesse Glick made changes -
          Assignee New: Kohsuke Kawaguchi [ kohsuke ]

          Kohsuke Kawaguchi added a comment -

          Fix to JENKINS-7216 should fix this, so I'm merging these two issues together.

          Kohsuke Kawaguchi added a comment - Fix to JENKINS-7216 should fix this, so I'm merging these two issues together.
          Kohsuke Kawaguchi made changes -
          Link New: This issue is duplicated by JENKINS-7216 [ JENKINS-7216 ]
          Kohsuke Kawaguchi made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 137321 ] New: JNJira + In-Review [ 187452 ]

            kohsuke Kohsuke Kawaguchi
            protocol7b protocol7b
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: