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

Builds fail because of "slave went offline during the build"

XMLWordPrintable

      Several times now I have builds that fail because of a "Looks like the node went offline during the build. Check the slave log for the details." message.

      That slave (a swarm slave) is still connected, but we want to reboot it's host. We have switched it to offline because it still had builds running, and we wanted to wait till they finish, but not have it accept new builds (that's the purpose of Offline, yes?)

      Of course that whole purpose is defeated if switching the slave to Offline also causes running builds to fail.

      Expected:

      • Have a way to cleanly shut down and disconnect an existing slave that has builds running, without disturbing its running builds in any way. Currently that is not possible.

          [JENKINS-17590] Builds fail because of "slave went offline during the build"

          Marc Günther created issue -
          Marc Günther made changes -
          Description Original: Several times now I have builds that fail because of a "Looks like the node went offline during the build. Check the slave log for the details." message.

          That slave (a swarm slave) is still connected. We have switched it to offline because it still had builds running, and we want to wait till they finish, but not have it accept new builds (that's the purpose of Offline, yes?)

          Of course that whole purpose is defeated if switching the slave to Offline also causes running builds to fail.

          Expected:
          - Have a way to cleanly shut down and disconnect an existing slave that has builds running, without disturbing that running builds in any way. Currently that is not possible.           		New: Several times now I have builds that fail because of a "Looks like the node went offline during the build. Check the slave log for the details." message.

          That slave (a swarm slave) is still connected, but we want to reboot it's host. We have switched it to offline because it still had builds running, and we wanted to wait till they finish, but not have it accept new builds (that's the purpose of Offline, yes?)

          Of course that whole purpose is defeated if switching the slave to Offline also causes running builds to fail.

          Expected:
          - Have a way to cleanly shut down and disconnect an existing slave that has builds running, without disturbing its running builds in any way. Currently that is not possible.
          Summary Original: Build fails because of "slave went offline during the build" New: Builds fail because of "slave went offline during the build"
          Andrew Erickson made changes -
          Affects Version/s New: current [ 10162 ]
          Andrew Erickson made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          Andrew Erickson made changes -
          Assignee New: Steven G Brown [ stevengbrown ]
          Marc Günther made changes -
          Component/s New: timestamper [ 15749 ]
          Andrew Erickson made changes -
          Link New: This issue duplicates JENKINS-16778 [ JENKINS-16778 ]
          Andrew Erickson made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Steven G Brown made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 148769 ] New: JNJira + In-Review [ 206577 ]

            stevengbrown Steven G Brown
            marc_guenther Marc Günther
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: