Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-8080

The default executor does not propagate missing task exit status correctly.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.2.3, 1.3.2, 1.4.1, 1.5.0
    • executor
    • None
    • Mesosphere Sprint 65

    Description

      The default executor is not handling a missing nested container
      exit status correctly. It is assuming the protobuf accessor was
      returning an Option rather than explicitly checking whether the
      `exit_status` field was present in the message.

      Attachments

        Activity

          People

            jamespeach James Peach
            jamespeach James Peach
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: