taharah opened a new issue, #34783: URL: https://github.com/apache/airflow/issues/34783
### Apache Airflow version Other Airflow 2 version (please specify below) ### What happened After upgrading Airflow from 2.5.3 to 2.6.3, none of our task logs for the ECS operator were being written to the configured file and S3 remote write handlers. ### What you think should happen instead Airflow task logs should be written to the configured handlers. ### How to reproduce Configure a remote write handler for a non-Kubernetes based executor. ### Operating System Amazon Linux 2 ### Versions of Apache Airflow Providers apache-airflow-providers-amazon = "7.4.1" apache-airflow-providers-celery = "3.3.4" ### Deployment Other ### Deployment details Airflow is deployed to Amazon ECS. ### Anything else The issue seems to be a result of the change from #28440. Specifically, the change to remove the handlers from the source logger (https://github.com/apache/airflow/pull/28440/files#diff-ad618185a072910e49c11770954af009d1cc070b120a4fde5f2fc095a588271bR704), which was not the previous behavior. I am happy to submit a change for this; however, want to get some direction on what others feel is the best path forward, e.g., making this behavior configurable or reverting to the original behavior. ### 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]
