You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This led to the migrations not being executed, yet for some reason the job still started, leading to all routing-api instances to be updated. WE only noticed it since the Log-api tried to register routes and failed since:
(/var/vcap/data/compile/routing-api/src/code.cloudfoundry.org/routing-api/db/client.go:79)
[2024-08-01 12:17:09] pq: column "instance_id" of relation "tcp_routes" does not exist
So it seems the a database that fails migrations does not block the job from starting.
Desired behavior
If a migration fails, the job refuses to start, this would prevent the component from running in a half-updated state. This would also flag whoever operates it to investigate directly, instead of only failing if another component later uses something that was part of the migration.
Affected Version
routing/0.301.0
The text was updated successfully, but these errors were encountered:
Looks like this is a problem with the migration that only affects postgres databases. Mysql is able to run the migration properly and assigns a default value to the instance_id column for existing rows, despite there not being a default set. Postgres fails here.
We're working on a fix to be released soon, and also investigating why the migration failure didn't cause routing-api to outright fail.
Current behavior
We had a bogus value in the database of the routing api leading to this error in the log:
This led to the migrations not being executed, yet for some reason the job still started, leading to all routing-api instances to be updated. WE only noticed it since the Log-api tried to register routes and failed since:
So it seems the a database that fails migrations does not block the job from starting.
Desired behavior
If a migration fails, the job refuses to start, this would prevent the component from running in a half-updated state. This would also flag whoever operates it to investigate directly, instead of only failing if another component later uses something that was part of the migration.
Affected Version
routing/0.301.0
The text was updated successfully, but these errors were encountered: