Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#51650 - [gitlab] Incomplete Sidekiq configuration
Attached to Project:
Community Packages
Opened by Johan (Johnnei) - Wednesday, 02 November 2016, 19:55 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Saturday, 05 November 2016, 07:01 GMT
Opened by Johan (Johnnei) - Wednesday, 02 November 2016, 19:55 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Saturday, 05 November 2016, 07:01 GMT
|
DetailsDescription:
Since GitLab 8.13 the Sidekiq configuration has been split to utilize more queues and stores the configuration in sidekiq_queues.yml. See https://about.gitlab.com/2016/10/22/gitlab-8-13-released/#sidekiq-queues for the notice of this change. The current gitlab-sidekiq.service doesn't include all the queues causing some of the GitLab features to not process tasks (ex. GitLab CI builds appear stuck). Additional info: * package version(s): gitlab 8.13.2-1 Steps to reproduce: install gitlab -- Included is a patch for the service file which uses the configuration file instead of manually supplying all the queues. 
gitlab-sidekiq.patch
(0.7 KiB)
|
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Saturday, 05 November 2016, 07:01 GMT
Reason for closing: Fixed
Saturday, 05 November 2016, 07:01 GMT
Reason for closing: Fixed
Comment by Sven-Hendrik Haase (Svenstaro) -
Saturday, 05 November 2016, 06:41 GMT
Thanks for the patch. Fix should be in rel -2.