[GitHub] [airflow] BobasB edited a comment on issue #9722: Airflow can't import DAG in UI and logs, but manual DAG trigger works

[GitBox <gi...@apache.org>]

BobasB edited a comment on issue #9722:
URL: https://github.com/apache/airflow/issues/9722#issuecomment-680962851


   Hi, 
   For those who interested in this issue. I have solved it for myself, and for short, the problem was init-container with git-sync for Webserver.
   In my deployment, I have Scheduler with init + side-car containers for git-sync, and for Webserver only side-car container for git-sync. 
   - Without network policies, git-sync container starts faster than Airflow Webserver and Airflow see this PATH for import and can import. 
   - When network policies were applied to Airflow, Airflow starts faster than side-car container (git-sync) and does NOT saw PATH for imports. (Also, if I start another Airflow Webserver with another PID/k8s port in already running container it works correctly).
   
   By adding git-sync init container to Webserver and Scheduler, dags volume always will be initialized before Airflow starts.
   
   Maybe it is Airflow bug, but the problem is: when Airflow starts and PATH doesn't exist it will never be visible for import in future.


----------------------------------------------------------------
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:
users@infra.apache.org