Uploaded image for project: 'Aurora'
  1. Aurora
  2. AURORA-175

thermos runner should discriminate failures using exit status

    XMLWordPrintableJSON

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.6.0
    • Component/s: Executor, Thermos
    • Labels:
      None
    • Sprint:
      Aurora Q3 Sprint 3, Aurora Q4 Sprint 1

      Description

      We do the correct thing on the executor side when there is a configuration/interpolation problem (report FAILURE.)

      On the thermos_runner side, we don't exit with a separate exit status for bad configuration, nor do we even pay attention to the exit status from the thermos executor. So when the runner exits unexpectedly, that's always treated as a LOST. Instead there should be a contract between the thermos_runner and thermos_executor about certain classes of failures indicated by exit statuses so that we can differentiate between legit LOST and FAILURE, for example if the user no longer exists on the box.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                wickman Brian Wickman
                Reporter:
                wickman Brian Wickman
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: