Repository navigation
Fix forge instance column types on PostgreSQL - #922
Merged
Merged
Conversation
The 0003 stubs declared their columns without a type. The real models derive it from the key each column references, but a stub has no relation to derive from, so PostgreSQL got text columns that cannot be compared to the uuid and varchar(64) keys they point at, and 0008 fails with "operator does not exist: text = uuid". 0007a converts them before 0008 runs. The parity test missed this because it compared column names only, on SQLite alone. It now records column types and re-runs every migration over a current PostgreSQL schema, which must leave it unchanged. 0010 needed a rerun guard to survive that, which it wanted anyway.
3 of 12 tasks
cbartz
added a commit
to canonical/github-runner-operators
that referenced
this pull request
Oct 15, 2026
…bases (#429) Pin GARM to the merge of cloudbase/garm#922. PostgreSQL databases that went through GARM's migration 0003 have text forge_instance_id columns, so migration 0008 failed with "operator does not exist: text = uuid" and GARM did not start (cloudbase/garm#920). The new migration 0007a converts those columns before 0008 runs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 0003 stubs declared their columns without a type. The real models derive it from the key each column references, but a stub has no relation to derive from, so PostgreSQL got text columns that cannot be compared to the uuid and varchar(64) keys they point at, and 0008 fails with "operator does not exist: text = uuid". 0007a converts them before 0008 runs.
The parity test missed this because it compared column names only, on SQLite alone. It now records column types and re-runs every migration over a current PostgreSQL schema, which must leave it unchanged. 0010 needed a rerun guard to survive that, which it wanted anyway.
Fixes #920