Sidekiq not restarted after database configuration change
Summary
During a database related configuration change for the applications, the sidekiq service was not restarted by a gitlab-ctl reconfigure
Steps to reproduce
- Make a change to the connection string for postgres
- Run
gitlab-ctl reconfigure
- Watch logs or pid's for the sidekiq services
What is the current bug behavior?
- Sidekiq is not restarted
What is the expected correct behavior?
Sidekiq relies on the connection string to talk to the right database server. If that changes, sidekiq should've been restarted.
Details of package version
11.4.4-ee on GitLab.com
Environment details
- Operating System: ubuntu
- Installation Target, remove incorrect values:
- VM: GCP
- Installation Type, remove incorrect values:
- Other: omnibus packaged installation
- Is there any other software running on the machine: no
- Is this a single or multiple node installation? multi
- Resources
- CPU: lots
- Memory total: lots more
Reference Work from: gitlab-com/gl-infra/production#532 (closed)