workspace HTTP 500 status when node no longer exists

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Incomplete
    • Priority: Major
    • Component/s: core
    • Environment:
      Linux, glassfish container

      When I clicked on the workspace folder for a job, I received a HTTP 500 status with the following exception:

      hudson.util.IOException2: remote file operation failed: /home/hudson/ci/hudson/slaves/slave_name/workspace/job_name at hudson.remoting.Channel@8bc54a:slave_name

      There was no full stack trace in the log files. The workspace exists in NFS but the actual node is no longer configured in Jenkins. It was removed and the job was not rebuilt after it was removed.

            Assignee:
            Unassigned
            Reporter:
            mezlight
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: