Migrating Zitadel version stuck on step47_fill_membereship_fields
🏬Self-hosted❓Question❌Unsolved
Environment: I'm self hosting Zitadel with a Postgres database.
Version: Currently running 2.66.3. Trying to update to 3.2.3.
Stack: I'm running Zitadel in a Kubernetes cluster in Azure and the Postgres database also in Azure running v15.12. Since it concerns membership fields, maybe it has something to do with the custom user roles? I'm setting the ZITADEL_INTERNALAUTHZ_ROLEPERMISSIONMAPPINGS arg to add some custom user roles on top of the existing roles.
What you expected to happen: The migration runs successfully.
What went wrong: The migration seems to get stuck on the migration step=47_fill_membership_fields. The migration has currently been running for 40 minutes, repeating the same warning message. See the attached .txt
It has been a while since I've had the time to update the Zitadel instance. My previous attempt for migrating from v2.66.3 to 2.77.3 was unsuccessful for the same reason. Since I had some spare time now I wanted to try the update again, this time to the newest currently available v3.2.3. However the same problem has occurred since last time, so I assume the problem is introduced somewhere between v2.66.3 and v2.77.3. Anyone any idea as to why this is happening?
Version: Currently running 2.66.3. Trying to update to 3.2.3.
Stack: I'm running Zitadel in a Kubernetes cluster in Azure and the Postgres database also in Azure running v15.12. Since it concerns membership fields, maybe it has something to do with the custom user roles? I'm setting the ZITADEL_INTERNALAUTHZ_ROLEPERMISSIONMAPPINGS arg to add some custom user roles on top of the existing roles.
What you expected to happen: The migration runs successfully.
What went wrong: The migration seems to get stuck on the migration step=47_fill_membership_fields. The migration has currently been running for 40 minutes, repeating the same warning message. See the attached .txt
It has been a while since I've had the time to update the Zitadel instance. My previous attempt for migrating from v2.66.3 to 2.77.3 was unsuccessful for the same reason. Since I had some spare time now I wanted to try the update again, this time to the newest currently available v3.2.3. However the same problem has occurred since last time, so I assume the problem is introduced somewhere between v2.66.3 and v2.77.3. Anyone any idea as to why this is happening?
