shivaam commented on issue #62246:
URL: https://github.com/apache/airflow/issues/62246#issuecomment-3988247316

   @vincbeck I was able to replicate the issue by resetting my DB and 
restarting airflow. Here is an analysis from Kiro and I can attache the whole 
log file if you need that. 
   
   ```
   Startup — all 4 bundles load and get "added":
   
   02:23:06.165 [info] DAG bundles loaded: team_alpha_dags, team_beta_dags, 
shared_dags, example_dags
   02:23:06.182 [info] Added new DAG bundle team_alpha_dags to the database
   02:23:06.188 [info] Added new DAG bundle team_beta_dags to the database
   02:23:06.192 [info] Added new DAG bundle shared_dags to the database
   02:23:06.193 [info] Added new DAG bundle example_dags to the database
   
   
   Less than 1 second later — team bundles can't be found in the DB:
   02:23:07.121 [warning] Bundle model not found for team_alpha_dags
   02:23:07.997 [warning] Bundle model not found for team_beta_dags
   
   Meanwhile the non-team bundles work fine:
   02:23:08.497 [info] Refreshing bundle shared_dags
   02:23:08.522 [info] Searching for files in shared_dags at 
/tmp/airflow/dag_bundles/shared_dags
   02:23:08.523 [info] Found 1 files for bundle shared_dags
   02:23:08.539 [info] Refreshing bundle example_dags
   02:23:08.558 [info] Found 61 files for bundle example_dags
   
   Then it repeats every ~5 seconds, never resolving — all the way to the end 
of the log at 02:32:02:
   02:23:11.300 [warning] Bundle model not found for team_alpha_dags
   02:23:11.306 [warning] Bundle model not found for team_beta_dags
   02:23:16.552 [warning] Bundle model not found for team_alpha_dags
   02:23:16.554 [warning] Bundle model not found for team_beta_dags
   ...
   02:32:02.184 [warning] Bundle model not found for team_alpha_dags
   02:32:02.188 [warning] Bundle model not found for team_beta_dags
   
   ```


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