PG::UndefinedTable: ERROR: relation "application_settings" does not exist (Puma && Sidekiq)

[lenkeybalis]

Dear all,

There is problem with my gitlab. During the initiallization I get the following error code. Basically I run these application on Kubernetes 1.18.3.

I use this with the simple configuration. I just rewrote from "ReplicaController"to "Deployment" kind. That's all. Everything is the same. Components:

• Gitlab 13.3.1
• Postgres 11
• Redis
• Minio (it is plus component what I want to use for my runner pod in the future)

I observed the following problem during the initalization:

Puma log and Sidekiq:

WARNING: PID file creation will be removed in Sidekiq 6.0, see #4045. Please use a proper process supervisor to start and manage your services WARNING: Logfile redirection will be removed in Sidekiq 6.0, see #4045. Sidekiq will only log to STDOUT PG::UndefinedTable: ERROR: relation "application_settings" does not exist LINE 1: SELECT "application_settings".* FROM "application_settings" ...

When I see this error in the logs, then in parallel also I see some error rows in postresql to.

Gitlab logs: 2015-07-18 13:35:40,282 INFO exited: puma (exit status 1; not expected) 2015-07-18 13:35:41,286 INFO spawned: 'puma' with pid 296 2015-07-18 13:35:41,287 INFO success: puma entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-07-18 13:35:41,628 INFO exited: sidekiq (exit status 1; not expected) 2015-07-18 13:35:41,286 INFO spawned: 'sidekiq' with pid 298 2015-07-18 13:35:42,629 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Could you please help me in this issue? Thank you.

Basically I use this stack with dyn provisoning sc. (Rook), Each components are working fine and the connection is also stable from my perspective. The strange things, the issue occured when I try to do a brand-new installation.

Thank you for your help!

[lacisz491]

Hi,

I have the same issue right now.

[Analect]

@lenkeybalis ... what was your fix for this? I am finding the same problem, having recently restored an old backup to the latest version 14.2.5. Thanks.