With the various Kubernetes abstractions most of Toolforge quota errors happen at the Job or Pod level and so not directly exposed to tool maintainers when creating or editing the tools.
Description
Description
Related Objects
Related Objects
Event Timeline
Comment Actions
I suspect updating jobs-framework-emailer to catch out of quota errors is the way to go here.
Comment Actions
Does emails: onfailure config for the job result in an email if the job fails to start due to a quota error?
Comment Actions
It appears there's no clear-cut answer to this. Quota issue isn't immediately causing an error. Job waits around for some time till quota is available and hence only gets delayed - good enough for cron jobs.