ido177 opened a new issue, #54544: URL: https://github.com/apache/airflow/issues/54544
### 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](https://github.com/apache/airflow/pull/41272). <img width="887" height="370" alt="Image" src="https://github.com/user-attachments/assets/2ac1df78-c63b-4467-9f25-f41f50ae37da"; /> ### 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? - [x] 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]
