fix(URGENT): pin umami to exact SHA (v1.38.0 has schema lineage mismatch) #3

2026-06-06T13:53:54+02:00

admin commented

2026-06-06 13:53:54 +02:00

URGENT: revert umami to the exact image SHA the working 120d-old pod is on. v1.38.0 (the latest postgresql-vX.Y.Z line) tries to apply a migration that needs a table the DB doesn't have (relation "event" does not exist), suggesting our pod runs a different schema lineage. SHA pin avoids that.

Detailed analysis + recovery plan in the commit message. tl;dr we need a v3.x migration plan eventually, but this stabilizes things first.

🤖 Generated with Claude Code

URGENT: revert umami to the exact image SHA the working 120d-old pod is on. v1.38.0 (the latest postgresql-vX.Y.Z line) tries to apply a migration that needs a table the DB doesn't have (`relation "event" does not exist`), suggesting our pod runs a different schema lineage. SHA pin avoids that. Detailed analysis + recovery plan in the commit message. tl;dr we need a v3.x migration plan eventually, but this stabilizes things first. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

admin added 1 commit 2026-06-06 13:53:54 +02:00

manifests: pin umami to exact image SHA (schema mismatch with v1.38.0) 7e6ea9d66c

Previous PR pinned `ghcr.io/umami-software/umami:postgresql-v1.38.0`.
The new pod crashlooped on Prisma:

  ERROR: relation "event" does not exist
  Migration name: 02_add_event_data
  Database error code: 42P01

The 120-day-old working pod's actual image is:
  ghcr.io/umami-software/umami@sha256:28f263fe06f79ebffa5a6a6e9b...

It runs an older umami build whose schema doesn't have the `event`
table that the v1 migration `02_add_event_data` operates on. The DB
has migrations 10-14 applied (newer than 02 by name) but 02 isn't in
its applied set -- likely a schema fork between the line our 120d pod
runs and the postgresql-vX.Y.Z line that v1.38.0 advances toward.

Pin to the exact SHA that the working pod uses, so pod restarts +
ArgoCD syncs both keep producing pods on the same known-good image
(cached on the node, no registry pull needed). Renovate also stops
chasing the broken upgrade path.

Proper fix (deferred): plan a v3.x migration. The version-checker
dashboard hint `postgresql-latest → 3.1` suggests umami v3.x dropped
the `postgresql-` prefix and is what we'd want long-term. That needs
a real DB migration plan since the schema lineage is genuinely
different from this image.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

admin merged commit dc64bb2d79 into main

2026-06-06 13:53:55 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: admin/felhom.eu#3