KulykDmytro opened a new issue #21548: URL: https://github.com/apache/airflow/issues/21548
### Apache Airflow version 2.2.3 (latest released) ### What happened Recently we're switched from `KubernetesExecutor` to `CeleryKubernetesExecutor` and faced with strange behaviour Tasks which are sent to `kubernetes` queue unable to provide logs in `webserver` while executing ``` *** Falling back to local log *** Log file does not exist: /opt/airflow/logs/sfmc_sync/notification_center_send_log/2022-02-12T07:00:00+00:00/6.log *** Fetching from: http://10.47.204.47:8793/log/sfmc_sync/notification_center_send_log/2022-02-12T07:00:00+00:00/6.log *** Failed to fetch log file from worker. [Errno 113] No route to host ``` webserver not even tried to reach tasks log over k8s api (like it happened when using `KubernetesExecutor`) ### What you expected to happen When task is executed on `kubernetes` queue (despite of executor chosen), logs from container's stdout should be provided to webserver upon request ### How to reproduce set executor to `CeleryKubernetesExecutor` set default queue to `celery` set additional queue for `kubernetes` send task for execution to `queue='kubernetes'` ### Operating System Linux 5.4.156-83.273.amzn2.x86_64 ### Versions of Apache Airflow Providers standard ones for official image ### Deployment Official Apache Airflow Helm Chart ### Deployment details EKS deployment ### Anything else _No response_ ### Are you willing to submit 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]
