-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Open
Labels
affected_version:3.0Issues Reported for 3.0Issues Reported for 3.0area:loggingkind:bugThis is a clearly a bugThis is a clearly a bugneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yet
Description
Apache Airflow version
3.0.4
If "Other Airflow 2 version" selected, which one?
2.10
What happened?
When running a task, if it transitions to the UP_FOR_RETRY state, no logs are displayed in the Airflow UI for that task attempt.
This seems to have been introduced in commit #41272.
What you think should happen instead?
Logs for all task attempts should be available in the UI, even if the attempt ends with UP_FOR_RETRY.
How to reproduce
- Deploy Airflow via the official Helm chart (1.18.0) in Kubernetes.
- Configure logging to store logs local on the worker pods.
- Run a DAG with a task that is expected to fail and retry.
- When the task enters the UP_FOR_RETRY state, check its logs in the UI.
Operating System
Debian GNU/Linux 12 (bookworm)
Versions of Apache Airflow Providers
Any — this is a core Airflow issue, not related to a specific provider version.
Deployment
Official Apache Airflow Helm Chart
Deployment details
Deployed in Kubernetes with local log storage (inside the pods).
Anything else?
I previously patched my own Airflow build and it worked
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
FencyC, nyu531 and assaf-xm
Metadata
Metadata
Assignees
Labels
affected_version:3.0Issues Reported for 3.0Issues Reported for 3.0area:loggingkind:bugThis is a clearly a bugThis is a clearly a bugneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yet