yonus opened a new issue, #62402: URL: https://github.com/apache/airflow/issues/62402
### Apache Airflow version 3.1.7 ### If "Other Airflow 3 version" selected, which one? _No response_ ### What happened? I deployed Airflow 3.1.7 using Helm chart 1.19.0. After deployment, everything works correctly. However, after some time (not immediately), accessing the Airflow UI results in: Internal Server Error (HTTP 500) Restarting the api-server pods immediately resolves the issue and the UI becomes accessible again. After some time, the issue reoccurs. When I investigated logs of api server, I see following error logs: **_PendingRollbackError: Can't reconnect until invalid transaction is rolled back. Please rollback() fully before proceeding (Background on this error)_** This behavior is reproducible. ### What you think should happen instead? Airflow UI should remain accessible without requiring manual restart of API server pods. ### How to reproduce Deploy Airflow 3.1.7 with Helm chart 1.19.0 Access UI successfully Wait for some time (hours) Try to access UI again Observe HTTP 500 Internal Server Error Restart api-server pods UI works again ### Operating System ubuntu ### Versions of Apache Airflow Providers apache-airflow-providers-amazon==9.21.0 apache-airflow-providers-cncf-kubernetes apache-airflow-providers-common-compat>=1.13.0 apache-airflow-providers-common-sql>=1.31.0 apache-airflow-providers-airbyte==5.3.2 apache-airflow-providers-slack==9.6.2 apache-airflow-providers-trino==6.4.2 pytz>=2023.3 ### Deployment Official Apache Airflow Helm Chart ### Deployment details _No response_ ### 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]
