Uploaded image for project: 'Marathon'
  1. Marathon
  2. MARATHON-7002

Create documentation on how to debug apps and packages that fail to launch

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Marathon 1.4.2
    • Component/s: Docs
    • Labels:
    • Sprint:
      Marathon Sprint 8-2017, Marathon Sprint 9-2017, Marathon Sprint 1.10-0

      Description

      At the moment we don't have documentation beyond this knowledgebase article on how to debug an application that fails to deploy.

      We're working on some tools in the CLI that will make this easier so we can wait until those are implemented before writing more documentation. This ticket is here to track that.

      These scenarios can happen:
      + User tries to install a package with a bad configuration, it never deploys (see DCOS-597).
      + User tries to install a package that requires more resources than the cluster has available.
      + User's Marathon app doesn't deploy

        Attachments

          Activity

            People

            • Assignee:
              suzanne Suzanne Scala (Inactive)
              Reporter:
              sunil Sunil Shah (Inactive)
              Team:
              Orchestration Team
              Watchers:
              Jason Gilanfarr (Inactive), Joel Hamill (Inactive), Lee Munroe (Inactive), Marco Monaco, Michael Gummelt (Inactive), Sunil Shah (Inactive), Suzanne Scala (Inactive)
            • Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: