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

No Veto reason is exposed for a task stuck in PENDING due to host constraints

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.5.0
    • Scheduler
    • None
    • Q2 Sprint 3, Q3 Sprint 1

    Description

      Tasks stuck in PENDING state due to unsatisfied host constraint don't have the reason set in TaskEvent.message. This makes the troubleshooting harder as neither UI nor aurora status can give any clues:

      INFO] role: mesos, env: test, name: monitoring, shard: 147, status: PENDING on None
      cpus: 0.5, ram: 512 MB, disk: 3072 MB
      	failure count: 0 (max 1)
      	events:
      		 2014-05-02 09:05:43 PENDING: None
      	metadata:
      		package: mesos/monitoring v14
      

      Attachments

        Issue Links

          Activity

            People

              maximk Maxim Khutornenko
              maximk Maxim Khutornenko
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Agile

                  Completed Sprints:
                  Q2 Sprint 3 ended 14/Jul/14
                  Q3 Sprint 1 ended 25/Jul/14
                  View on Board

                  Slack

                    Issue deployment