Open anxstj opened 4 years ago
Hello, same problem here, jobs failed with a traceback and no notification, because of a requirements.yml containing a repository which is not accessible. (thanks for the bug report, btw, which helped us find the issue).
I am going to submit this as a technical improvement item to be escalated, because our exception handling in tasks could strongly benefit from some more eyes on it.
We have a small set of internal exception types, but we're apparently not using them right. In this case, we should be specifically catching this AwxTaskError
. It doesn't make any sense to surface that in a traceback, because the point in code where the exception is raised is merely passing on the information that the dependency failed. What the user should be interested in is:
Hi all,
this is currently true, and I find a workaround thanks to this issue
Just go to /api/v2/jobs/YOURJOBNUMBER/
and follow the link at "project_updates" key
Under project_updates, follow "stdout" key and you will find the root cause.
ISSUE TYPE
SUMMARY
If a Job fails to update its project (or project dependencies) then the error details will show a traceback as error message.
ENVIRONMENT
STEPS TO REPRODUCE
EXPECTED RESULTS
The job should fail with a meaningful error message. (e.g. "The project update has failed. See job id 12345 for details.")
ACTUAL RESULTS
The job fails with a stack trace.
ADDITIONAL INFORMATION
api/v2/jobs/29218/:
api/v2/project_updates/29219/:
api/v2/project_updates/29219/stdout/?format=txt:
api/v2/projects/560/: