Details
-
Story
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
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
- is related to
-
AURORA-911 Scheduling vetos are only displayed for the first task in a TaskGroup
- Resolved