You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On deployment via ArgoCD, the airflow app toggled between Healthy and Progressing. There was a problem with a pod airflow-sync-users-789b8c9b64-5vb6t. EVENTS recorded:
Back-off restarting failed container sync-airflow-users in pod airflow-sync-users-789b8c9b64-m6xwp_dare-airflow(b003810c-711a-437a-9bec-04b4fc7c705b)
LOGS recorded:
/home/airflow/.local/lib/python3.10/site-packages/flask_limiter/extension.py:336 UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring-a-storage-backend for documentation about configuring the storage backend.
Traceback (most recent call last):
File "/mnt/scripts/sync_users.py", line 146, in <module>
from airflow.www.fab_security.sqla.models import User, Role
ModuleNotFoundError: No module named 'airflow.www.fab_security.sqla.models'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/mnt/scripts/sync_users.py", line 148, in <module>
from flask_appbuilder.security.sqla.models import User, Role
File "/home/airflow/.local/lib/python3.10/site-packages/flask_appbuilder/security/sqla/models.py", line 48, in <module> assoc_permissionview_role = Table( File "<string>", line 2, in __new__
File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/util/deprecations.py", line 375, in warned
return fn(*args, **kwargs)
File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/sql/schema.py", line 596, in __new__
raise exc.InvalidRequestError(
sqlalchemy.exc.InvalidRequestError: Table 'ab_permission_view_role' is already defined for this MetaData instance. Specify 'extend_existing=True' to redefine options and columns on an existing Table object.
The problematic pod cited image harbor.ukserp.ac.uk/dare/airflow/base:1.1.3 so the problem is the container which wasn't previously specified in values.
The text was updated successfully, but these errors were encountered:
I updated the DARE-Teleport chart version from 1.10.1 to 1.13.6. This meant I got an updated Airflow configuration from charts/teleport/values.yaml:
to 1.13.6 charts/teleport/values.yaml:
On deployment via ArgoCD, the airflow app toggled between Healthy and Progressing. There was a problem with a pod airflow-sync-users-789b8c9b64-5vb6t. EVENTS recorded:
LOGS recorded:
The problematic pod cited image
harbor.ukserp.ac.uk/dare/airflow/base:1.1.3
so the problem is the container which wasn't previously specified invalues
.The text was updated successfully, but these errors were encountered: