Merge requests and pipeline are stuck after 16.8.1 security upgrade
Summary
Gitlab's security upgrade from release 16.7.3-ee to 16.8.1-ee generate 2 main issues on our docker self hosted env. It's now impossible for us to do a merge request and to run a pipeline.
- No changes have been made on our CI/CD (gitlab-ci.yml) nor on our runners, all projects are impacted
- Same issue occur on project created on 16.8.1 release with default gitlab-ci.yml
- Our runners are still active and accessible for our gitlab and our projects
Steps to reproduce
- Have a running docker self hosted gitlab, with repositories and their working CI-CD.
- Stop docker container
- Pull 16.8.1-ee image
- Start docker container with this new image, and wait end of migration
- Do a merge request, or launch a pipeline
Example Project
Issue has been detected on a gitlab docker image, I don't have enough ressources to create a new infra
What is the current bug behavior?
- Creating a merge requests is stuck with message "Your merge request is almost ready!" and an infinite spinner. Few days later this status is still the same
- We are not in capacity to manually trigger a pipeline, as we still have an infinite spinner displayed instead of the form allowing to set variables
- Scheduled pipelines have stopped to be executed
What is the expected correct behavior?
- Created merge requests display the status of linkinded pipeline then offer the possibility to do the merge if no conflict are detected
- Pipeline can be manually triggered, on chosen branch with or without setting variables
- Scheduled pipelines are run at specified time interval
Relevant logs and/or screenshots
Newly created merge request
Merge request created 4 days before and still blocked
Manually triggered pipeline stuck before having the possibility to define varialble
Scheduled pipeline with next run plan for 2 days ago
Output of checks
Results of GitLab environment info
sudo gitlab-rake gitlab:env:info
System information System: Proxy: no Current User: git Using RVM: no Ruby Version: 3.1.4p223 Gem Version: 3.4.22 Bundler Version:2.5.4 Rake Version: 13.0.6 Redis Version: 7.0.15 Sidekiq Version:7.1.6 Go Version: unknown GitLab information Version: 16.8.1-ee Revision: 1242b447720 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 13.12 URL: https://scm.wider.ai HTTP Clone URL: https://scm.wider.ai/some-group/some-project.git SSH Clone URL: git@scm-ssh.wider.ai:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: no Using Omniauth: yes Omniauth Providers: google_oauth2 GitLab Shell Version: 14.33.0 Repository storages: - default: unix:/var/opt/gitlab/gitaly/gitaly.socket GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Gitaly - default Address: unix:/var/opt/gitlab/gitaly/gitaly.socket - default Version: 16.8.1 - default Git Version: 2.42.0
Results of GitLab application Check
As mentioned in recent tickets, we also have Sidekiq issue related to redis 6 release
sudo gitlab-rake gitlab:check SANITIZE=true
Checking GitLab subtasks ...
Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 14.33.0 ? ... OK (14.33.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Gitaly ...
Gitaly: ... default ... OK
Checking Gitaly ... Finished
Checking Sidekiq ...
Sidekiq: ... Running? ... no Try fixing it: sudo -u git -H RAILS_ENV=production bin/background_jobs start For more information see: doc/install/installation.md in section "Install Init Script" see log/sidekiq.log for possible errors Please fix the error above and rerun the checks.
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Reply by email is disabled in config/gitlab.yml
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab App ...
Database config exists? ... yes Tables are truncated? ... skipped All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Cable config exists? ... yes Resque config exists? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Systemd unit files or init script exist? ... skipped (omnibus-gitlab has neither init script nor systemd units) Systemd unit files or init script up-to-date? ... skipped (omnibus-gitlab has neither init script nor systemd units) Projects have namespace: ... 11/9 ... yes 10/12 ... yes 76/14 ... yes 7/15 ... yes 7/16 ... yes 10/21 ... yes 9/23 ... yes 9/25 ... yes 33/28 ... yes 7/29 ... yes 32/32 ... yes 49/34 ... yes 33/35 ... yes 49/36 ... yes 7/37 ... yes 9/39 ... yes 58/41 ... yes 9/42 ... yes 32/43 ... yes 10/44 ... yes 9/46 ... yes 66/47 ... yes 68/48 ... yes 72/50 ... yes 72/51 ... yes 32/52 ... yes 76/53 ... yes 76/54 ... yes 76/59 ... yes 9/60 ... yes 9/61 ... yes 9/62 ... yes 7/64 ... yes 7/65 ... yes 49/66 ... yes 49/67 ... yes 49/69 ... yes 7/70 ... yes 10/71 ... yes 7/72 ... yes 9/73 ... yes 10/74 ... yes 106/75 ... yes 76/76 ... yes 76/77 ... yes 9/78 ... yes 49/79 ... yes Redis version >= 6.0.0? ... yes Ruby version >= 3.0.6 ? ... yes (3.1.4) Git user has default SSH configuration? ... yes Active users: ... 4 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes Elasticsearch version 7.x-8.x or OpenSearch version 1.x ... skipped (Advanced Search is disabled) All migrations must be finished before doing a major upgrade ... skipped (Advanced Search is disabled)
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished
Possible fixes
We didn't found any workaround