We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apache Airflow version:
Kubernetes version (if you are using kubernetes) (use kubectl version):
kubectl version
Environment:
uname -a
What happened: Task log can't be shown on Web-Server when the task runs failed, while log can be shown normally when the task success
*** Log file does not exist: /home/airflow/airflow/logs/dag_id/task_id/2021-06-28T00:00:00+08:00/28.log *** Fetching from: http://:8793/log/dag_id/task_id/2021-06-28T00:00:00+08:00/28.log *** Failed to fetch log file from worker. Unsupported URL protocol
What you expected to happen: The task log should be shown normally when the task runs failed.
The Hostname info doesn't be written into the task instance table, so the webserver can't get the corresponding hostname.
How to reproduce it: Just run a dag and make its task fail to reproduce the bug.
Anything else we need to know: I have fixed it in my env and will commit a PR to fix it.
The text was updated successfully, but these errors were encountered:
Thanks for opening your first issue here! Be sure to follow the issue template!
Sorry, something went wrong.
Looks like another duplicate to #13692.
Sure, I will track it on the other issue.
No branches or pull requests
Apache Airflow version:
Kubernetes version (if you are using kubernetes) (use
kubectl version
):Environment:
uname -a
): Linux 3.10.0-514.21.1.el7.x86_64What happened:
Task log can't be shown on Web-Server when the task runs failed, while log can be shown normally when the task success
What you expected to happen:
The task log should be shown normally when the task runs failed.
The Hostname info doesn't be written into the task instance table, so the webserver can't get the corresponding hostname.
How to reproduce it:
Just run a dag and make its task fail to reproduce the bug.
Anything else we need to know:
I have fixed it in my env and will commit a PR to fix it.
The text was updated successfully, but these errors were encountered: