TwentyT
Twentyβ€’2y agoβ€’
24 replies
πŸ…ΉπŸ…°πŸ†ˆπŸ…±πŸ…΄πŸ…΄

Upgrade issue to 0.22

Running on my test server to see if upgrade process from 0.11 to 0.22

During start of containers a migration is run automatically so I assume migrate is not needed anymore so I am not running yarn database:migrate:prod manually anymore

when i first run workspace-sync i receive an error (see comment, too long message)

then I run command:prod upgrade-0.22 it also receives error:
[Nest] 519  - 08/01/2024, 10:56:31 AM     LOG [UpdateMessageChannelSyncStageEnumCommand] Running command on workspace 75f6e77a-ec52-43fd-af2b-5e1ca8319b2e failed
[Nest] 519  - 08/01/2024, 10:56:31 AM   ERROR [UpdateMessageChannelSyncStageEnumCommand] Migration failed for workspace 75f6e77a-ec52-43fd-af2b-5e1ca8319b2e: type "workspace_6zezc5oiagj6yqldcepfgb226.messageChannel_syncStage_enum" does not exist
[Nest] 519  - 08/01/2024, 10:56:31 AM     LOG [UpdateMessageChannelSyncStageEnumCommand] Command completed

if I then run workspace-sync again it works and then I can run command:prod upgrade-0.22 again without error followed up with workspace-sync without error.

Is this expected behaviour or is there a better way then just "rerun both commands twice"?

I noticed that if I run
yarn command:prod upgrade-0.22:fix-object-metadata-id-standard-id

before running workspace-sync i seem to get around this "run twice" behaviour, is this the/a correct solution?
Was this page helpful?