[GitHub] [airflow] Oduig commented on issue #29442: Logging from inside on_failure_callback not propagated with Cloud Composer

["Oduig (via GitHub)" <gi...@apache.org>]

Oduig commented on issue #29442:
URL: https://github.com/apache/airflow/issues/29442#issuecomment-1425430654

   Here are the contents of our Google Storage bucket:
   
   ![airflow-bucket](https://user-images.githubusercontent.com/3661031/218043922-b8d79e48-3b73-4515-b11b-6deed8c3c9e4.png)
   
   The logs for the individual DAGs are there though:
   
   ![airflow-bucket-2](https://user-images.githubusercontent.com/3661031/218043931-4b6c81ce-0513-4084-93c5-05e8b5f81f29.png)
   
   When I `kubectl exec` into the `airflow-scheduler` deployment, I see that the logs folder is mounted with GCS fuse as expected:
   
   ![airflow-scheduler-logs-1](https://user-images.githubusercontent.com/3661031/218045389-95bf150b-cdc0-4b25-a740-348897562bf1.png)
   
   In the $AIRFLOW_HOME directory, I see a `logs/scheduler` folder with recent files in it, but all the files are empty:
   
   ![airflow-scheduler-logs-2](https://user-images.githubusercontent.com/3661031/218045629-13cf60b1-800e-4e42-9a28-b42996639cb5.png)
   
   Let me know if there is anything else I can check
   


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org