Problem with migration
Hey everyone,
I was running Twenty on version
Then I updated my worker to use
In my worker logs I’m getting this error during the upgrade process: - currentVersion (migrating to): 1.7.6 - fromWorkspaceVersion: 1.6.0 - 1 commands [Nest] ERROR [UpgradeCommand] Error in workspace b752764a-2dfd-4ffc-80ae-07307fbdd7c4: Unable to run the upgrade command. Aborting the upgrade process. Please ensure that all workspaces are on at least the previous minor version (1.6.0). If any workspaces are not on the previous minor version, roll back to that version and run the upgrade command again. Do you have any procedure or recommended steps I should follow to properly upgrade from
Should I roll back and update version by version? Thanks in advance 🙏
v1.2.1 without issues.Then I updated my worker to use
:latest in order to get the newest version, but now everything is broken.In my worker logs I’m getting this error during the upgrade process: - currentVersion (migrating to): 1.7.6 - fromWorkspaceVersion: 1.6.0 - 1 commands [Nest] ERROR [UpgradeCommand] Error in workspace b752764a-2dfd-4ffc-80ae-07307fbdd7c4: Unable to run the upgrade command. Aborting the upgrade process. Please ensure that all workspaces are on at least the previous minor version (1.6.0). If any workspaces are not on the previous minor version, roll back to that version and run the upgrade command again. Do you have any procedure or recommended steps I should follow to properly upgrade from
1.2.1 to the latest version without breaking the worker?Should I roll back and update version by version? Thanks in advance 🙏
8 Replies
You have to upgrade it procedurally so 1.2.0 > 1.3.0 > 1.4.0 and so on, do you have a backup?
i tried but all the time i have a error with the manifest version
i haven't a backup 🙂
I saw in a channel something like an auto-update CLI. Can it help me later?
Hello there
Unfortunately the auto upgrade CLI won't help you
It will be available later and starting from a specific version
As bob said you need upgrade your instance incrementally
You can still try to downgrade you, could be corrupted instance, back to your current workspace version in database and proceed to upgrade incrementally again
hello @prastoin ! So in my docker compose, I tried to downgrade but I had a message current version 1.7.6 but in compose it’s 1.2.1, maybe a file in the project to modify ?
Hey have you followed below step from general guidelines ?
Upgrade the version by changing the TAG value in the .env file near your docker-compose. ( We recommend consuming major.minor version such as v0.53 )You can also double check your twenty instance version by running
echo $APP_VERSION or env | grep APP_VERSION in your twenty-server containerHello @bob and @prastoin !
So ! I went back to 1.2.1 for my SERVER and WORKER (before i just forgot to choose the same version for both services)
It work with a small error, but it's fine
After, i move to the 1.3.1, now to the 1.4.1 and my objective for today it's to have the last one 🙂
I will give you some feedback 🙂
but this one :
You have to upgrade it procedurally so 1.2.0 > 1.3.0 > 1.4.0 and so on, do you have a backup?
I think on the documentation, you need to say if for SERVER and WORKER
Hello there
I'm not sure to understand
Are you building a custom twenty docker image ?
If not official images covers both WORKER and SERVER under the same TAG env variable
Please be sure to restart all of your pods and follow general guidelines