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

   ### Apache Airflow version
   
   3.1.0
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   DAG processor status icon mistakenly shows unhealthy status at random moment 
of time. The container has no errors and wasn't restarted.
   ### Screen recording
   
https://github.com/user-attachments/assets/02403ad5-9f6d-4aa0-9896-79026fb517c6
   
   ### What you think should happen instead?
   
   DAG processor status icon should show the actual status of the component.
   
   ### How to reproduce
   
   Use AIrlfow and take a look at DAG processor icon.
   
   ### Operating System
   
   Debian GNU/Linux 12 (bookworm)
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-celery==3.12.3
   apache-airflow-providers-common-compat==1.7.4
   apache-airflow-providers-common-io==1.6.3
   apache-airflow-providers-common-sql==1.28.1
   apache-airflow-providers-fab==2.4.3
   apache-airflow-providers-google==18.0.0
   apache-airflow-providers-http==5.3.4
   apache-airflow-providers-postgres==6.3.0
   apache-airflow-providers-redis==4.3.1
   apache-airflow-providers-smtp==2.2.1
   apache-airflow-providers-standard==1.8.0
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   Deployed on GKE with extended image based on `apache/airflow:slim-3.1.0` and 
Helm chart 1.18.0.
   Migrated from 3.0.6.
   
   ### 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