grepthat commented on issue #11696:
URL: https://github.com/apache/airflow/issues/11696#issuecomment-714726775


   Some more info on this:
   I think #11729 should fix the issue for access to the pod logs (I'm not a 
Kubernetes expert though).
   
   The other error I mentioned (about getting an error 400 when trying to fetch 
the logs) was related to setting a different uid/gid in the helm install. The 
worker pod's were launched with that uid, so the default user was not airflow. 
I got this log from the worker-pod:
   
   ```bash
   $~ kubectl logs simpledagtask1-12f123a06db04f9684628ff0dedd96cb -n airflow
   Traceback (most recent call last):
     File "/home/airflow/.local/bin/airflow", line 5, in <module>
       from airflow.__main__ import main
   ModuleNotFoundError: No module named 'airflow'
   ```
   
   After removing the `--set uid=1000` from the helm install I could launch 
worker pods and read logs.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to