"410 : Gone" error during repo sync when using Jira DVCS integration
Summary
Though the Jira DVCS integration is successful and works as expected, GitLab throws 410 : Gone
during initial repo sync. Think this is because DVCS tries to create web-hooks for real-time data collection from GitLab using v3 API and this not supported at the moment.
Steps to reproduce
- Configure Jira DVCS as per: https://docs.gitlab.com/ee/integration/jira/dvcs.html#configure-jira-for-dvcs
- Sync repos.
What is the current bug behavior?
GitLab throws 410
error during initial sync.
What is the expected correct behavior?
GitLab should either suppress the error or support creation of web-hooks through v3 API wrapper.
Relevant logs and/or screenshots
Sep 3, 2021 @ 14:18:19.358 18.184.99.232 - - [03/Sep/2021:12:18:19 +0000] "GET /api/v3/repos/group/proj/hooks HTTP/1.1" 410 62 "-" "Apache-HttpClient/4.5.13 (Java/1.8.0_292)" 313 0.021 [gitlab-gitlab-webservice-default-8181] [] 10.20.20.20:8181 62 0.020 410 d6b8i3e68j3b0p0248u01b7n56389198
Output of checks
Results of GitLab environment info
GitLab 14.0.7-ee
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
- Add dummy endpoints to accept web-hook creation requests in https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/api/v3/github.rb to avoid throwing
410
until Real-time updates in Jira dev panel with DVCS connector is rolled out.