[GitHub] [airflow] potiuk commented on issue #19784: Airflow python exception at login

[GitBox <gi...@apache.org>]

potiuk commented on issue #19784:
URL: https://github.com/apache/airflow/issues/19784#issuecomment-977004264


   The problem is that you did not change "defaultAirflowTag" but you rebuilt your image with "latest" version - which has been upgraded to 2.2.2. 
   
   If you want to keep 2.1.0 version of Airlfow you should explicitly base your image on it:
   In your docker image you shoud use:
   
   ```
   FROM apache/airflow:2.1.0-python3.7
   ```
   
   The `latest` tag is moving whenever we release new version.
   
   The problem is that your "custom" image is likely based on 2.2.2 version (which is current latest) but since you have `useDefaultImageForMigration`, you are using `defaultAirflowTag` which is probably 2.1.0 as this was the default version released together with the chart. Which means that migration did not actually migrate the database as needed by Airflow 2.2.2. 
   
   The solution is that you should make sure that both - your custom image and your `defaultAirflowTag` point to the same version. Likely what should work for you is to replace the `FROM` line with 2.1.0 (verify if your `defaultAirflowTag` is also 2.1.0, rebuild and push your image and make sure the new image is pulled when you deploy Airflow.
   
   


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org