Sidekiq Cron is not being updated based on defaults defined in GitLab source

Summary

It looks like we are not updating Sidekiq cron configurations. Still not clear if only in development or production as well.

Steps to reproduce

???

possible instructions:

  1. setup a new instance with geo cron using old times
  2. revert code to include new time ranges
  3. check sidekiq monitoring tab and see old times again

What is the current bug behavior?

Sidekiq Cron from long lived instances is not updating to the newly defined defaults here: https://gitlab.com/gitlab-org/gitlab-ee/blob/b958e271cdf9fe46bbb07b65dd28f0c6ba12dbd1/config/initializers/1_settings.rb#L315

What is the expected correct behavior?

My instance should have been updated to have /1 (each minute) instead of /5 (each 5 minutes)

Relevant logs and/or screenshots

this is what I have on testing/production instances: (which match) sidekiq-production

and this is what I have on my development instances: (which are older than that 11 months ago change) sidekiq-dev-machine

Possible fixes

???

Edited Oct 15, 2018 by Gabriel Mazetto
Assignee Loading
Time tracking Loading