Sidekiq gets stuck and does not recover when issuing `rails db:migrate`
Summary
This is a followup for this comment.
When running Gitlab using GDK, issuing bundle exec rails db:migrate
as part of this documentation causes sidekiq to get stuck. The process does not recover for days until restarted.
Expected results:
- sidekiq does not get stuck
- if it gets stuck, Gitlab should be able to recover it
See linked issue for more context.
Steps to reproduce
Example Project
What is the current bug behavior?
What is the expected correct behavior?
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)