starred/vikunja-go-vikunja

Fork 0

mirror of https://github.com/go-vikunja/vikunja.git synced 2026-03-03 00:46:57 -05:00

"Migration failed: migration 20260123000717 failed: pq: cannot drop index idx_18922_primary because constraint idx_18922_pr imary on table webhooks requires it #803

New issue

Closed

opened 2026-02-27 15:14:38 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-27 15:14:38 -05:00

Owner

Originally created by @Eldiabolo21 on GitHub (Feb 9, 2026).

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?

Screenshots

No response

Originally created by @Eldiabolo21 on GitHub (Feb 9, 2026). ### Pre-submission checklist - [x] 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_

deekerman closed this issue

2026-02-27 15:14:41 -05:00

deekerman commented

2026-02-27 15:14:42 -05:00

Author

Owner

@kolaente commented on GitHub (Feb 9, 2026):

Did you upgrade from 1.0.0 or earlier?

@kolaente commented on GitHub (Feb 9, 2026): Did you upgrade from 1.0.0 or earlier?

deekerman commented

2026-02-27 15:14:42 -05:00

Author

Owner

@Eldiabolo21 commented on GitHub (Feb 10, 2026):

Sorry, completely forgot.

Yes this is an Upgrade from 1.0.0.

@Eldiabolo21 commented on GitHub (Feb 10, 2026): Sorry, completely forgot. Yes this is an Upgrade from 1.0.0.

deekerman commented

2026-02-27 15:14:42 -05:00

Author

Owner

@hackschnitzel09 commented on GitHub (Feb 10, 2026):

I see the same issue

@hackschnitzel09 commented on GitHub (Feb 10, 2026): I see the same issue

deekerman commented

2026-02-27 15:14:43 -05:00

Author

Owner

@vikunja-bot-app[bot] commented on GitHub (Feb 24, 2026):

This issue has been fixed in #2288, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

@vikunja-bot-app[bot] commented on GitHub (Feb 24, 2026): This issue has been fixed in #2288, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/vikunja-go-vikunja#803

No description provided.

Rows
Columns