"Migration failed: migration 20260123000717 failed: pq: cannot drop index idx_18922_primary because constraint idx_18922_pr imary on table webhooks requires it #2215
Description
Pre-submission checklist
- I have searched for existing open or closed issue reports with the same problem.
Description
Hi, I just upgraded, to Vikunja v1.1.0. The setup is running in k8s, I'm using the official helm chart and just set the image tag manually.
When the new pod is created I get:
2026/02/09 18:12:46 failed to create modcache index dir: mkdir /.cache: permission denied
time=2026-02-09T18:12:46.170Z level=INFO msg="Using config file: /etc/vikunja/config.yml"
time=2026-02-09T18:12:46.171Z level=INFO msg="Running migrations…"
time=2026-02-09T18:12:46.274Z level=ERROR msg="Migration failed: migration 20260123000717 failed: pq: cannot drop index idx_18922_primary because constraint idx_18922_pr
imary on table webhooks requires it"
I've upgraded my instance a couple of times now, so not sure if theres any issue with continues upgrades?
DB is in CNPG, all looks healthy, heres some info:
k cnpg -n vikunja status vikunja-cluster
Cluster Summary
Name vikunja/vikunja-cluster
System ID: 7599013140810571803
PostgreSQL Image: ghcr.io/cloudnative-pg/postgresql:17
Primary instance: vikunja-cluster-2
Primary start time: 2026-01-30 15:08:36 +0000 UTC (uptime 243h13m37s)
Status: Cluster in healthy state
Instances: 3
Ready instances: 3
Size: 597M
Current Write LSN: 0/24000060 (Timeline: 2 - WAL File: 000000020000000000000024)
Continuous Backup status
Not configured
Streaming Replication status
Replication Slots Enabled
Name Sent LSN Write LSN Flush LSN Replay LSN Write Lag Flush Lag Replay Lag State Sync State Sync Priority Replication Slot
---- -------- --------- --------- ---------- --------- --------- ---------- ----- ---------- ------------- ----------------
vikunja-cluster-1 0/24000060 0/24000060 0/24000060 0/24000060 00:00:00 00:00:00 00:00:00 streaming async 0 active
vikunja-cluster-3 0/24000060 0/24000060 0/24000060 0/24000060 00:00:00 00:00:00 00:00:00 streaming async 0 active
Instances status
Name Current LSN Replication role Status QoS Manager Version Node
---- ----------- ---------------- ------ --- --------------- ----
vikunja-cluster-2 0/24000060 Primary OK BestEffort 1.27.1 k8s-01-1
vikunja-cluster-1 0/24000060 Standby (async) OK BestEffort 1.27.1 k8s-03
vikunja-cluster-3 0/24000060 Standby (async) OK BestEffort 1.27.1 k8s-04
any ideas?
Vikunja Version
1.1.0
Browser and version
No response
Can you reproduce the bug on the Vikunja demo site?
No
Screenshots
No response