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

Nodes disappear if "# of executors" is set to 0

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • Jenkins 2.7.2

      When "# of executors" is set to 0 for a node, not only does the node disappear from the listing (as abayer pointed out to me), but the node will 404 on it's /computer/$node page.
      The work around is either to edit the config.xml and restart jenkins or use the script feature. The linked gist contains a script to set the number of executors to 2 which was used a temporary fix in our case.

      [0] - https://gist.github.com/pono/8ab92fddb9461cd62e45923b910ce81f

        1. Screen Shot 2018-02-20 at 11.15.35.png
          Screen Shot 2018-02-20 at 11.15.35.png
          75 kB

          [JENKINS-41182] Nodes disappear if "# of executors" is set to 0

          Pono Takamori created issue -
          Pono Takamori made changes -
          Summary Original: Nodes disappear is "# of executors" is set to 0 New: Nodes disappear if "# of executors" is set to 0

          Daniel Beck added a comment -

          How are you setting nodes count to 0?

          Daniel Beck added a comment - How are you setting nodes count to 0?

          noob alot added a comment - - edited

          I see this issue too.

          I set the executors to 0 by going to the node's config page, changing the executor number, and saving.

          Then the node disappears.

          The way I got the node back was to edit the node's config in JENKINS_HOME/nodes/NODE_NAME/config.xml, changing the executors count, and restarting my Jenkins instance. Then the node reappeared.

          noob alot added a comment - - edited I see this issue too. I set the executors to 0 by going to the node's config page, changing the executor number, and saving. Then the node disappears. The way I got the node back was to edit the node's config in JENKINS_HOME/nodes/NODE_NAME/config.xml, changing the executors count, and restarting my Jenkins instance. Then the node reappeared.
          Oleg Nenashev made changes -
          Link New: This issue is duplicated by JENKINS-41385 [ JENKINS-41385 ]

          Alec Matschiner added a comment -

          When I had set the node executor to 0 I observed all of the same issues described in the description here. I then tried to just create a new node with the same name, that didn't work since its still in the file system. As noob alot (nice name) mentioned you can edit the config and change the # of executors. I also noticed deleting that node's directory, restarting Jenkins, and then I'm able to create a new node with that name but then you'll have to reconfigure it.

          I'd like to suggest maybe adding more of a warning when when someone is trying to change the executors to 0 in the node config page.

          Alec Matschiner added a comment - When I had set the node executor to 0 I observed all of the same issues described in the description here. I then tried to just create a new node with the same name, that didn't work since its still in the file system. As noob alot (nice name) mentioned you can edit the config and change the # of executors. I also noticed deleting that node's directory, restarting Jenkins, and then I'm able to create a new node with that name but then you'll have to reconfigure it. I'd like to suggest maybe adding more of a warning when when someone is trying to change the executors to 0 in the node config page.
          Oleg Nenashev made changes -
          Labels New: newbie-friendly
          Andrew Bayer made changes -
          Assignee Original: Andrew Bayer [ abayer ]
          Kseniia Nenasheva made changes -
          Assignee New: Kseniia Nenasheva [ ks_nenasheva ]
          Daniel Beck made changes -
          Link New: This issue is duplicated by JENKINS-44902 [ JENKINS-44902 ]

            ks_nenasheva Kseniia Nenasheva
            pono Pono Takamori
            Votes:
            5 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: