Better log when no agent is available for schedule Computing session #1814
Labels
effort:easy
Need to understand only a specific region of codes (good first issue, easy).
Milestone
When we try to schedule a
Computing session
but there is no available agent in the scaling group, the log is like below.The problem is that the above logging is very confusing when the reason why there is no actual available agent is not image mismatch.
Let's add more comprehensible and detail logs.
The text was updated successfully, but these errors were encountered: