ZITADELZZITADEL
Powered by
PallabP
ZITADEL•14mo ago•
17 replies
Pallab

Need help upgrading form v2.55.8 to v2.67.1

I have an instance of Zitadel running on EKS that uses PostgreSQL running on RDS.

Current Zitadel Version: v2.55.8
Upgrade Version: v2.67.1

Postgres Version: 15.7

The instance was deployed using the official helm chart. The 
zitadel-setup
zitadel-setup
 job gets stuck at the following migration step

caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:130" migration step=29_init_fields_for_project_grant
caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:130" migration step=29_init_fields_for_project_grant


This is the corresponding log from the database.
2025-01-29 13:00:46 UTC:10.230.9.194(42190):postgres@zitadel:[29296]:STATEMENT: INSERT INTO eventstore.events2 (
instance_id
, "owner"
, aggregate_type
, aggregate_id
, revision
, creator
, event_type
, payload
, "sequence"
, created_at
, "position"
, in_tx_order
) VALUES
($1, $2, $3, $4, $5, $6, $7, $8, $9, statement_timestamp(), EXTRACT(EPOCH FROM clock_timestamp()), $10)
RETURNING created_at, "position";
2025-01-29 13:00:46 UTC:10.230.27.208(56588):postgres@zitadel:[28383]:ERROR: duplicate key value violates unique constraint "events2_pkey"
2025-01-29 13:00:46 UTC:10.230.27.208(56588):postgres@zitadel:[28383]:DETAIL: Key (instance_id, aggregate_type, aggregate_id, sequence)=(250999327709734704, project, 253045174010121988, 3515980) already exists.
2025-01-29 13:00:46 UTC:10.230.9.194(42190):postgres@zitadel:[29296]:STATEMENT: INSERT INTO eventstore.events2 (
instance_id
, "owner"
, aggregate_type
, aggregate_id
, revision
, creator
, event_type
, payload
, "sequence"
, created_at
, "position"
, in_tx_order
) VALUES
($1, $2, $3, $4, $5, $6, $7, $8, $9, statement_timestamp(), EXTRACT(EPOCH FROM clock_timestamp()), $10)
RETURNING created_at, "position";
2025-01-29 13:00:46 UTC:10.230.27.208(56588):postgres@zitadel:[28383]:ERROR: duplicate key value violates unique constraint "events2_pkey"
2025-01-29 13:00:46 UTC:10.230.27.208(56588):postgres@zitadel:[28383]:DETAIL: Key (instance_id, aggregate_type, aggregate_id, sequence)=(250999327709734704, project, 253045174010121988, 3515980) already exists.


I've tried running a 
zitadel setup cleanup
zitadel setup cleanup
 from the debug pod as documented here: https://github.com/zitadel/zitadel-charts/blob/main/README.md

However, the issue still persists and I'm unsure on how to resolve this. I tried searching the forum but haven't been able to figure out the right approach.

Any help is appreciated.

Thanks.
GitHub
zitadel-charts/README.md at main · zitadel/zitadel-charts
This repository contains Helm charts for running ZITADEL in Kubernetes - zitadel/zitadel-charts
ZITADEL banner
ZITADELJoin
ZITADEL - Identity infrastructure, simplified for you.
4,374Members
Resources
Recent Announcements

Similar Threads

Was this page helpful?

Similar Threads

upgrading from v2.65.10 to v2.66.0 error at setup
boblack_zockerBboblack_zocker / questions-help-bugs
6mo ago
Upgrading from v2.x.x to v4.x.x
Keyur BholeKKeyur Bhole / questions-help-bugs
2mo ago
Problem with upgrade from 2.66.1 to 2.67.6
nluNnlu / questions-help-bugs
14mo ago