Actions
Feature #9023
closedIf a component is not satisfiable, report and fail the job
Status:
Duplicate
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Story points:
-
Description
It is currently impossible to know why a component stays queued. One option is that it requests a node that does not exist on that cluster. If this is the case, it would be nice to report that to the job and mark it as failed.
Related issues
Actions