Tony
New image causing errors
We run a self-hosted version of Windmill on AWS ECS. The task config was set to use the latest Windmill image. We had not restarted the tasks in months. Yesterday I restarted them & they seem to have picked up a new Windmill image. Now the logs have some new errors in them. Here is an example:
Sql error: error occurred while decoding column "job_kind": invalid value "flownode" for enum JobKind error=SqlErr(ColumnDecode { index: ""job_kind"", source: "invalid value "flownode" for enum JobKind" }) target=windmill_common::error span={"email":"admin@windmill.dev","method":"GET","trace_id":"c9b78efa-344b-4ccc-b8bd-8c2b53544252","uri":"/api/w/design-generation/jobs_u/get/0195d35e-dbfa-ae09-801f-ad7dc63afda2?no_logs=true","username":"admin","workspace_id":"design-generation","name":"request"}
Is there a correct way to upgrade (or even to rollback) that we should follow to extricate ourselves from this situation?
20 replies