Geo Sidekiq-cron jobs don't get re-enabled automatically
@xiaogang_gitlab and another customer experienced a problem where the Geo Sidekiq tasks were not running for some reason.
The problem is that the state of Sidekiq-cron jobs is stored in Redis as a hash key in the form resque:gitlab:cron_job:<job name>
.
In the Sidekiq initializer, we disable secondary Sidekiq jobs here: https://gitlab.com/gitlab-org/gitlab-ee/blob/v9.1.0-ee/config/initializers/sidekiq.rb#L49-52
The problem is that we never RE-ENABLE these jobs, and thus the state persists even if the Redis cache is cleared.