potiuk commented on pull request #19597:
URL: https://github.com/apache/airflow/pull/19597#issuecomment-972725321
Hmm. Looks like we are testing the right thing:
1) first we download the image
ghcr.io/apache/airflow/main/prod/python3.6:ed09464667f7d83e25b4eb377839b873dbc5e925
- i pulled it and it contains latest changes from the PR:
~/.local/lib/python3.6/site-packages/airflow/utils/db.py:
```
def check_migrations(timeout):
"""
Function to wait for all airflow migrations to complete.
:param timeout: Timeout for the migration in seconds
:return: None
"""
from alembic.runtime.environment import EnvironmentContext
```
2) Then we use that image and create:
ghcr.io/apache/airflow/main/kubernetes/python3.6:latest from it with embedded
DAGs and kubernetes_executor_templates
3) then that image is loaded to kind:
```
kind load docker-image --name airflow-python-3.6-v1.18.15
ghcr.io/apache/airflow/main/kubernetes/python3.6:latest
```
4) and it used by the helm installation:
```
kind load docker-image --name airflow-python-3.6-v1.18.15
ghcr.io/apache/airflow/main/kubernetes/python3.6:latest
```
So everythin there looks legit. The problem is that when webserver starts
(for example) it raises this "migration" error.
I believe "check-migrations" was fixed by this PR (but it did not fix the
problem). Previously we saw this error in output in "migration" container - but
now we see similar error in webserw.
https://github.com/apache/airflow/actions/runs/1473732053 (see the artifacts
- pick any of them and go to worker/containers/webserver logs).
--
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]
