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

   ### Apache Airflow version
   
   3.1.5
   
   ### If "Other Airflow 3 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   We are using airflow 3.1.5 and my providers are as follows 
   
   ```bash
   RUN pip install --no-cache-dir mysqlclient==2.2.7
   RUN pip install --no-cache-dir aiomysql
   # Airflow 3.1 required provider for KubernetesExecutor
   RUN pip install --no-cache-dir 
apache-airflow-providers-cncf-kubernetes==10.8.2
   RUN pip install --no-cache-dir connexion[flask]>=3.0
   RUN pip install --no-cache-dir "flask-appbuilder<=5.0.0"
   RUN pip install --no-cache-dir apache-airflow-providers-fab==3.0.1
   RUN pip install --no-cache-dir apache-airflow-providers-google
   RUN pip install --no-cache-dir apache-airflow-providers-celery
   RUN pip install --no-cache-dir apache-airflow-providers-slack==9.6.1
   ```
   
   We are consistently facing the issue, almost daily. And we need to rollout 
our deployment everytime we face this isse. The issue start from `JWT token is 
not valid: Signature has expired 
[airflow.api_fastapi.auth.managers.base_auth_manager` then goes till 
`sqlalchemy.exc.PendingRollbackError: Can't reconnect until invalid transaction 
is rolled back` 
   
   auth manager i am using is `auth_manager: 
"airflow.providers.fab.auth_manager.fab_auth_manager.FabAuthManager"` but in 
error i see `[airflow.api_fastapi.auth.managers.base_auth_manager` can anybody 
help me with this
   
   ### What you think should happen instead?
   
   Maybe I am using the auth manager incorrectly, like if we are using fab, 
then why is it going for `base_auth_manager` here? We have the jmt token 
configured in our helm as well. We get this daily; can anyone help us with this 
on a priority basis?
   
   ### How to reproduce
   
   I am not sure how to do that, it's totally related to the auth manager.
   
   ### Operating System
   
   linux
   
   ### Versions of Apache Airflow Providers
   
   RUN pip install --no-cache-dir mysqlclient==2.2.7
   RUN pip install --no-cache-dir aiomysql
   # Airflow 3.1 required provider for KubernetesExecutor
   RUN pip install --no-cache-dir 
apache-airflow-providers-cncf-kubernetes==10.8.2
   RUN pip install --no-cache-dir connexion[flask]>=3.0
   RUN pip install --no-cache-dir "flask-appbuilder<=5.0.0"
   RUN pip install --no-cache-dir apache-airflow-providers-fab==3.0.1
   RUN pip install --no-cache-dir apache-airflow-providers-google
   RUN pip install --no-cache-dir apache-airflow-providers-celery
   RUN pip install --no-cache-dir apache-airflow-providers-slack==9.6.1
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   We have deployed it on standard GKE cluster with celery executors and 
kuberenetes executors.
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] 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