I have set up an external sidekiq node using omnibus gitlab but I keep getting this error whenever I do merge requests, run pipelines etc.
Currently, sidekiq is turned off in the main gitlab installation. Correct gitaly and Redis configurations have been made. The pipelines also run successfully but the error is thrown right after
Configuration for external sidekiq
==> /var/log/gitlab/gitlab-rails/application.log <==
2023-02-02T08:22:33.315Z: Cannot obtain an exclusive lease for ci/pipeline_processing/atomic_processing_service::pipeline_id:31945. There must be another instance already in execution.
==> /var/log/gitlab/gitlab-rails/application_json.log <==
{"severity":"ERROR","time":"2023-02-02T08:22:33.315Z","correlation_id":"01GR8KGR2H4KEADPHGQKMJNQJW","message":"Cannot obtain an exclusive lease for ci/pipeline_processing/atomic_processing_service::pipeline_id:31945. There must be another instance already in execution."}
==> /var/log/gitlab/gitlab-rails/application.log <==
2023-02-02T08:40:08.147Z: Ci::StuckBuilds::DropScheduledService: Cleaning scheduled, timed-out builds
==> /var/log/gitlab/gitlab-rails/application_json.log <==
{"severity":"INFO","time":"2023-02-02T08:40:08.147Z","correlation_id":"c1034b183451f242808e6052f10b0746","message":"Ci::StuckBuilds::DropScheduledService: Cleaning scheduled, timed-out builds"}
==> /var/log/gitlab/gitlab-rails/application.log <==
2023-02-02T09:20:11.681Z: Ci::StuckBuilds::DropRunningService: Cleaning running, timed-out builds
Anyone faced this error before or can share the correct way of configuring things to avoid this?
