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

Display All Scheduling Veto Reasons for PENDING tasks

    XMLWordPrintableJSON

Details

    • Story
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.8.0
    • Reliability, Scheduler
    • None

    Description

      Recently I was triaging an instance that would not schedule, and although I was validating many possibilities, I did get sidetracked when I saw that 'Insufficient RAM' was listed as the reason.

      In fact, there was also insufficient Disk, CPU, and hosts, as this was a task which had a dedicated constraint.

      In order to give more information, we should ensure we're exposing all Vetoes to help narrow if there is just one resource preventing scheduling, or many (all resources may point to a lack of hosts overall, for instance).

      I did notice both AURORA-377 and AURORA-911, but both seem unrelated to this.

      Attachments

        Issue Links

          Activity

            People

              maximk Maxim Khutornenko
              yasumoto Joe Smith
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: