Mailroom fails to Start in RC2
Summary
Mailroom fails to start on RC2 due to a NameError
What is the current bug behavior?
Mailroom continuously tries to restart to no avail.
What is the expected correct behavior?
Mailroom should start with no complaints.
Relevant logs and/or screenshots
2017-08-15_17:28:58.62597 sidekiq-asap01 mailroom: Runit: starting mail_room
2017-08-15_17:28:59.36018 sidekiq-asap01 mailroom: bundler: failed to load command: mail_room (/opt/gitlab/embedded/bin/mail_room)
2017-08-15_17:28:59.36024 sidekiq-asap01 mailroom: NameError: uninitialized constant #<Class:Gitlab::Redis::Queues>::DEFAULT_REDIS_QUEUES_CONFIG_FILE_NAME
2017-08-15_17:28:59.36026 sidekiq-asap01 mailroom: /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/redis/queues.rb:26:in `config_file_name'
2017-08-15_17:28:59.36036 sidekiq-asap01 mailroom: /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/redis/wrapper.rb:38:in `_raw_config'
2017-08-15_17:28:59.36041 sidekiq-asap01 mailroom: /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/redis/wrapper.rb:122:in `fetch_config'
2017-08-15_17:28:59.36051 sidekiq-asap01 mailroom: /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/redis/wrapper.rb:112:in `raw_config_hash'
2017-08-15_17:28:59.36056 sidekiq-asap01 mailroom: /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/redis/wrapper.rb:75:in `url'
2017-08-15_17:28:59.36061 sidekiq-asap01 mailroom: /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/mail_room.rb:38:in `fetch_config'
2017-08-15_17:28:59.36066 sidekiq-asap01 mailroom: /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/mail_room.rb:13:in `config'
2017-08-15_17:28:59.36072 sidekiq-asap01 mailroom: /opt/gitlab/embedded/service/gitlab-rails/config/mail_room.yml:4:in `<main>'
2017-08-15_17:28:59.36077 sidekiq-asap01 mailroom: /opt/gitlab/embedded/lib/ruby/2.3.0/erb.rb:864:in `eval'
2017-08-15_17:28:59.36082 sidekiq-asap01 mailroom: /opt/gitlab/embedded/lib/ruby/2.3.0/erb.rb:864:in `result'
2017-08-15_17:28:59.36086 sidekiq-asap01 mailroom: /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/lib/mail_room/configuration.rb:18:in `initialize'
2017-08-15_17:28:59.36093 sidekiq-asap01 mailroom: /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/lib/mail_room/cli.rb:38:in `new'
2017-08-15_17:28:59.36098 sidekiq-asap01 mailroom: /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/lib/mail_room/cli.rb:38:in `initialize'
2017-08-15_17:28:59.36104 sidekiq-asap01 mailroom: /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/bin/mail_room:5:in `new'
2017-08-15_17:28:59.36109 sidekiq-asap01 mailroom: /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/mail_room-0.9.1/bin/mail_room:5:in `<top (required)>'
2017-08-15_17:28:59.36114 sidekiq-asap01 mailroom: /opt/gitlab/embedded/bin/mail_room:22:in `load'
2017-08-15_17:28:59.36119 sidekiq-asap01 mailroom: /opt/gitlab/embedded/bin/mail_room:22:in `<top (required)>'
2017-08-15_17:28:59.37241 sidekiq-asap01 mailroom: Runit: waiting 5 seconds before restarting mail_room
Output of checks
GitLab.com
Possible fixes
We were able to work around this problem by setting the env variable manually:
echo /opt/gitlab/embedded/service/gitlab-rails/config/resque.yml > /opt/gitlab/etc/gitlab-rails/env/GITLAB_REDIS_QUEUES_CONFIG_FILE