Database migration failed while using helm chart

[GEEugene]

Is there an existing issue for this?

• [X] I have searched the existing issues

Kong version ($ kong version)

3.6.1

Current Behavior

When I use helm chart to deploy kong to K8s cluster with standalone Postgre database, I got error whith migrations job process: stack traceback: [C]: in function 'error' /usr/local/share/lua/5.1/kong/cmd/utils/migrations.lua:60: in function 'up' /usr/local/share/lua/5.1/kong/cmd/migrations.lua:204: in function 'cmd_exec' /usr/local/share/lua/5.1/kong/cmd/init.lua:31: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:31> [C]: in function 'xpcall' /usr/local/share/lua/5.1/kong/cmd/init.lua:31: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:15> (command line -e):7: in function 'inline_gen' init_worker_by_lua(nginx.conf:324):44: in function <init_worker_by_lua(nginx.conf:324):43> [C]: in function 'xpcall' init_worker_by_lua(nginx.conf:324):52: in function <init_worker_by_lua(nginx.conf:324):50>

Helm chart version is 2.38.0

Expected Behavior

Database migrations goes well

Steps To Reproduce

No response

Anything else?

No response

[ADD-SP]

@GEEugene Thanks for your report, could you please give us the steps to reproduce this issue?

[StarlightIbuki]

@GEEugene Thanks for your report, could you please give us the steps to reproduce this issue?

Especially which version are you migrating from? @GEEugene

[github-actions[bot]]

This issue is marked as stale because it has been open for 14 days with no activity.

[github-actions[bot]]

Dear contributor,

We are automatically closing this issue because it has not seen any activity for three weeks. We're sorry that your issue could not be resolved. If any new information comes up that could help resolving it, please feel free to reopen it.

Your contribution is greatly appreciated!

Please have a look our pledge to the community for more information.

Sincerely, Your Kong Gateway team