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

Can't Reassign Job to a New Node After Deleting Existing Node

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Platform: All, OS: All

      When 1 node besides the master node exists and is deleted, then any jobs that
      were assigned to it cannot be re-assigned without editing the config.xml file
      directly.

      Steps to reproduce:
      1. Create 1 (and only 1) node (excluding the master node).
      2. Assign a job to the new node.
      3. Delete the node.
      4. Attempting to run the job fails because the node is missing and there isn't
      any way to alter it now from the job configuration page.

      Possible Solution:
      1. Ensure the node selection option is still available on the job
      configuration page even when no other nodes beside the master are available.
      2. Default a job back to the master node when the node is was assigned to is
      missing.

      Note that this error is valid if there is only 1 node besides the master node
      and it is deleted.

          [JENKINS-2905] Can't Reassign Job to a New Node After Deleting Existing Node

          Alan Harder added a comment -

          making this section also appear if assignedLabel value is non-null, so you can
          then uncheck it (or if you do nothing it will then be assigned to master, since
          that's the only choice in the listbox).

          Alan Harder added a comment - making this section also appear if assignedLabel value is non-null, so you can then uncheck it (or if you do nothing it will then be assigned to master, since that's the only choice in the listbox).

          Code changed in hudson
          User: : mindless
          Path:
          trunk/hudson/main/core/src/main/resources/hudson/model/AbstractItem/configure-common.jelly
          trunk/www/changelog.html
          http://fisheye4.cenqua.com/changelog/hudson/?cs=15595
          Log:
          [FIXED JENKINS-2905] Show assigned-node section of config page whenever
          assignedLabel!=null, so job can be unassigned from a node even after
          last slave node has been deleted.

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : mindless Path: trunk/hudson/main/core/src/main/resources/hudson/model/AbstractItem/configure-common.jelly trunk/www/changelog.html http://fisheye4.cenqua.com/changelog/hudson/?cs=15595 Log: [FIXED JENKINS-2905] Show assigned-node section of config page whenever assignedLabel!=null, so job can be unassigned from a node even after last slave node has been deleted.

          Alan Harder added a comment -
              • Issue 2642 has been marked as a duplicate of this issue. ***

          Alan Harder added a comment - Issue 2642 has been marked as a duplicate of this issue. ***

            mindless Alan Harder
            psykod psykod
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: