Error in DB Migration: v2 migrate from v1
I have decided to upgrade one of the worker groups and apply the new migrations but getting this error constantly:
2025-02-21T06:16:12.576439429Z 2025-02-21T06:16:12.575768Z INFO windmill-api/src/db.rs:93: Acquired global PG lock
2025-02-21T06:16:12.587240719Z 2025-02-21T06:16:12.587029Z INFO windmill-api/src/db.rs:130: Started applying migration 20250201124748: v2 migrate from v1
2025-02-21T06:18:32.191178681Z 2025-02-21T06:18:32.190955Z INFO windmill-api/src/db.rs:156: Finished applying migration 20250201124748
2025-02-21T06:18:32.232113713Z Error: Error migrating db: Migrating database: while executing migration 20250201124748: error returned from database: value too long for type character varying(50)
29 Replies
What should I check or attempt to rectify this?
GitHub
bug: Migration from v1 to v2 fails · Issue #5345 · windmill-labs/wi...
Describe the bug Updating the image on one of the worker groups started the migration process. Once it got to the v1 to v2 migration it fails after a few minutes and then the container terminates a...
curious how come your tags were so long, it would usually happen for dedicated workers
Cool. Let me check. Thanks @rubenf
Interesting. I found this tag in the queue: "playground:flow/f/sql_flows/eflow_exceptions_investigate_byhubid_to_dwh"
it's a dedicated worker job
Looks like db migration has been completed but there is also an error from python:
you're not using our images are you?

are you in a very tight environment where it wouldn't be able to download python ?
Nope. Running a docker swarm with 5 nodes that have full outbound access to the internet
investigating
Let me know if I can assist in anyway
what are your volume mounts?
For the workers I have this mount setup on each docker node which points to the same dedicate share:

The same is for the worker dependncy cache and lsp cache and index

@ramkubcp1:~$ docker volume inspect windmill_worker_logs_prod
[
{
"CreatedAt": "2024-09-17T13:48:11Z",
"Driver": "local",
"Labels": null,
"Mountpoint": "/var/lib/docker/volumes/windmill_worker_logs_prod/_data",
"Name": "windmill_worker_logs_prod",
"Options": {
"device": "//10.0.20.210/worker_logs",
"o": "addr=10.0.20.210,username=windmill.service,password=***,vers=3.0",
"type": "cifs"
},
"Scope": "local"
}
]
somehow your filesystem doesn't support symlinking
Odd. Is this something new in the newer images?
it uses uv which install python instead of relying on the system python
but uv to install python require symlinking
which your system doesn't seem to support for some reasons
remove the windmill_worker_dependency_cache_prod volumes for now
Would it require the containers to run in priveledged mode?
no
Let me try
the error is this one:
ok removing the cache mount seems to resolve the error
How will this affecting the caching on the scripts?
yes, they won't be persistent across worker restarts
ok cool
I can live with that 👍
All looks good. Thanks
Thank you for your time @rubenf I appreciate it
sorry for the trouble, i'm still not too sure how the symlink error happens
No worries. Just glad to be up and running again with Windmill 🙂