Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incompatibility with PostgreSQL 16 - "failed to insert cluster lock: unexpected result" #1136

Open
MatheusFlausino opened this issue Oct 7, 2024 · 0 comments

Comments

@MatheusFlausino
Copy link

MatheusFlausino commented Oct 7, 2024

I'm encountering a problem deploying Kong with Helm chart on AWS EKS while using PostgreSQL 16 with AWS RDS.
I'm using chats version kong/kong 2.41.1 and when the pods to EKS the deployment fails, displaying the following error message:

/usr/local/share/lua/5.1/kong/cmd/utils/migrations.lua:115: [PostgreSQL error] failed to insert cluster lock: unexpected result
stack traceback:
[C]: in function 'error'
/usr/local/share/lua/5.1/kong/cmd/utils/migrations.lua:115: in function 'up'
/usr/local/share/lua/5.1/kong/cmd/utils/migrations.lua:204: in function 'cmd_exec'
...

However, this issue does not occur when using PostgreSQL 13.3. The problem seems specific to PostgreSQL versions higher than 14.

Actual Behavior:

Deploy the Kong Helm chart using PostgreSQL 16 as the database.
Connection with AWS RDS, exists because create 2 tables and insert values on table lock.
Observe the error during the migration phase: [PostgreSQL error] failed to insert cluster lock: unexpected result.
The migration status command (kong migrations status) outputs the following:
error_kong

Configurations in migration:

migrations:
  preUpgrade: true
  postUpgrade: true
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant