Jira integration not working
Summary
The Jira integration has stopped working recently. Things we note:
- The integration does not work for new repositories, as in we can't reference issues. For some of our repos which were transferred to Gitlab about a month ago, this still works as before, but for new ones it does not. They all use the same template. So we cannot reference an issue in a MR title/description as e.g. OTA-989; for some existing repos, this turns into a link to Jira, for the new ones (transferred from BitBucket last week) this does not.
- Closing issues from commits/MR's does not work anymore. No mention on Jira is made when a MR is merged, as was done previously. This has stopped working alltogether for all repos.
Steps to reproduce
The only thing we changed about the integration is upgrading Gitlab over time.
What is the current bug behavior?
- No linking is done to issues.
- No mentioning on Jira of GitLab actions.
What is the expected correct behavior?
The functional integration as advertised.
Relevant logs and/or screenshots
When clicking Test settings
, we get an error saying We tried to send a request to the provided URL but an error occurred
. I tried to have a look at the logs (production.log
), but the only thing I found was
Started GET "/<redacted_organisation>/<redacted_project>/services/jira/test" for <redacted_ip> at 2017-03-09 10:15:09 +0000
Processing by Projects::ServicesController#test as HTML
Parameters: {"namespace_id"=>"<redacted_organisation>", "project_id"=>"<redacted_project>", "id"=>"jira"}
Started GET "/<redacted_organisation>/transformations/merge_requests/71/ci_status" for <redacted_ip> at 2017-03-09 10:15:09 +0000
Processing by Projects::MergeRequestsController#ci_status as JSON
Parameters: {"namespace_id"=>"<redacted_organisation>", "project_id"=>"transformations", "id"=>"71"}
Completed 200 OK in 61ms (Views: 0.3ms | ActiveRecord: 6.7ms)
Scoped order and limit are ignored, it's forced to be batch order and batch size
Scoped order and limit are ignored, it's forced to be batch order and batch size
JiraService Send message ERROR: https://otainsight.atlassian.net - Unauthorized
Redirected to <redacted_our_gitlab_instance>/<redacted_organisation>/<redacted_project>/services/jira/edit
Completed 302 Found in 1454ms (ActiveRecord: 5.3ms)
Started GET "/<redacted_organisation>/<redacted_project>/services/jira/edit" for <redacted_ip> at 2017-03-09 10:15:10 +0000
Output of checks
Results of GitLab environment info
System information
System: Debian 8.7
Proxy: no
Current User: git
Using RVM: no
Ruby Version: 2.3.3p222
Gem Version: 2.6.6
Bundler Version:1.13.7
Rake Version: 10.5.0
Redis Version: 3.2.5
Sidekiq Version:4.2.7
GitLab information
Version: 8.17.2-ee
Revision: 474978d
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
DB Version: 9.6.1
URL: https://<redacted_our_instance>
HTTP Clone URL: https://<redacted_our_instance>/some-group/some-project.git
SSH Clone URL: git@<redacted_our_instance>:some-group/some-project.git
Elasticsearch: no
Geo: no
Using LDAP: no
Using Omniauth: yes
Omniauth Providers: google_oauth2, bitbucket
GitLab Shell
Version: 4.1.1
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks/
Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Possible fixes
Checking GitLab Shell ...
GitLab Shell version >= 4.1.1 ? ... OK (4.1.1)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
4/2 ... ok
4/3 ... ok
4/5 ... ok
4/7 ... ok
4/8 ... ok
4/9 ... ok
4/10 ... ok
4/11 ... ok
4/12 ... ok
4/13 ... ok
4/14 ... ok
4/15 ... ok
4/16 ... ok
4/17 ... ok
4/18 ... ok
4/19 ... ok
4/20 ... ok
4/21 ... ok
4/22 ... ok
4/23 ... ok
4/24 ... ok
4/25 ... ok
4/26 ... ok
4/28 ... ok
4/29 ... ok
4/30 ... ok
4/32 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
Reply by email is disabled in config/gitlab.yml
Checking Reply by email ... Finished
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured with autocrlf=input? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
projects have namespace: ...
4/2 ... yes
4/3 ... yes
4/5 ... yes
4/7 ... yes
4/8 ... yes
4/9 ... yes
4/10 ... yes
4/11 ... yes
4/12 ... yes
4/13 ... yes
4/14 ... yes
4/15 ... yes
4/16 ... yes
4/17 ... yes
4/18 ... yes
4/19 ... yes
4/20 ... yes
4/21 ... yes
4/22 ... yes
4/23 ... yes
4/24 ... yes
4/25 ... yes
4/26 ... yes
4/28 ... yes
4/29 ... yes
4/30 ... yes
4/32 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.3.3)
Your git bin path is "/opt/gitlab/embedded/bin/git"
Git version >= 2.7.3 ? ... yes (2.10.2)
Active users: 13
Elasticsearch version 2.4.x? ... yes (2.4.1)
Elasticsearch has plugin delete-by-query installed? ... no
Checking GitLab ... Finished