hterik opened a new issue, #28116:
URL: https://github.com/apache/airflow/issues/28116
### Description
Some times tasks are marked as failed by the scheduler or other internal
airflow components, with the reason being known by the scheduler, but not
surfaced to users. Instead the task is just marked as failed, without any
indication why in the Logs-tab nor under Task instance details. Only way to
figure out is for admins to go through the scheduler-logs.
Example: `{scheduler_job.py:1526} ERROR - Detected zombie job: .....`, marks
the task as failed.
Here the UI looks like this, with the logs-tab being only showing an empty
attempt of fetching log files from worker:
If there is a need to hide potential scheduler-secrets from users, there
should at least be some generic error message saying that the task was not run
to completion because of internal scheduler error. So that users know if they
should debug task-logic themselves, or involve admins in debugging the
infrastructure.
Looking at `taskinstance.handle_failure`-function it seem like most the code
for handling such errors is already very centralized. Is there a way to attach
the error there onto the taskinstance itself, for use in the UI? Or is it
possible to merge the relevant log streams to show in the Logs-tab?
### Use case/motivation
_No response_
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
