carlosjourdan opened a new issue, #46159:
URL: https://github.com/apache/airflow/issues/46159

   ### Official Helm Chart version
   
   1.15.0 (latest released)
   
   ### Apache Airflow version
   
   2.10.4
   
   ### Kubernetes Version
   
   1.29.8
   
   ### Helm Chart configuration
   
   executor: "CeleryKubernetesExecutor"
   
   config:
     celery_kubernetes_executor:
       kubernetes_queue: k8s
   
   airflowVersion: 2.10.4
   
   images:
       airflow:
           repository: apache/airflow
           tag: 2.10.4
   
   
   ### Docker Image customizations
   
   None.
   
   ### What happened
   
   When running any task on the `k8s` queue, the logs portion of the DAGs 
displays the message `Could not read served logs: 
HTTPConnectionPool(host='hello-world-task1-8n9u83p0', port=8793): Max retries 
exceeded with url: 
/log/dag_id=hello_world/run_id=manual__2025-01-28T02:16:39.751530+00:00/task_id=task1/attempt=1.log
 (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 
0x7f89fd5e6b70>: Failed to resolve 'hello-world-task1-8n9u83p0' ([Errno -3] 
Temporary failure in name resolution)"))`
   
   ### What you think should happen instead
   
   Logs should be available on the web interface.
   
   ### How to reproduce
   
   Deploy helm chart with config above, and run a simple hello world dag
   
   ```python
   @dag(
       schedule=None,
       start_date=pendulum.datetime(2100, 1, 1, tz="UTC"),
       catchup=False,
   )
   def hello_world():
       
       @task(queue='k8s')
       def task1():
           print("Hello World")
       
       task1()
   
   hello_world()
   ```
   
   ### 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]

Reply via email to