CrashLoopBackOff for most pods due to DB migration failing when upgrading to chart version 8.6.1 and Airflow version 2.3.0. #667
Replies: 3 comments
-
I highly recommend against using Airflow 2.3.0, as there were many bugs. You might want to try using Airflow 2.3.4, and see if that fixes your issue. https://airflow.apache.org/docs/apache-airflow/stable/release_notes.html#airflow-2-3-4-2022-08-23 |
Beta Was this translation helpful? Give feedback.
-
@thesuperzapper Haven't commented here in a while, I guess the main question would be if there's a recommended way for doing Airflow version upgrades with this Chart. I'm currently using the Terraform Helm release for managing the deployments and I always see errors when upgrading version, mostly related to DB migration issues, does't really matter which version I'm trying to migrate to, right now I need to jump from |
Beta Was this translation helpful? Give feedback.
-
trying to upgrade to
|
Beta Was this translation helpful? Give feedback.
-
Hello,
We've been using this Helm chart for a little bit more that a year now, to deploy it we are using the Terraform helm_release resource. Right now, I'm trying to update one release from chart version
8.5.2
to8.6.1
and Airflow version from2.1.x
to2.3.0
, I'm getting the following error in thedb-migrations
container:Clients are using the following Dockerfile to create the custom image:
requirements.txt content:
it seems is trying to drop something but not sure what it its, this instance is running a lot of DAGs and it is possible that some tasks were running at the time of the upgrade, is there any previous steps or precautions that we need to take before updating the chart version or Airflow version? could you please help us to shed some light on this?
Please let me know if you might need further information.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions