Service template doesn't reload new configuration
Summary
When I update the configuration in service template, I could see the value updated, but Gitlab doesn't use this value. I tried a reconfigure & restart, nothing changes.
Steps to reproduce
- Open service templates
- enable HipChat (same bug with Jira) integration
- make an update in any repo, the message will appear on the room
- update configuration to use another room
- the previous is still used
- change the server or the key, everything is ignored
What is the current bug behavior?
app updates values but don't use them
What is the expected correct behavior?
app updates values and use them
Output of checks
See logs in gitlab-ctl tail, for example, I put an invalid server in hipchat and I have the warn
WARN: HipChat::Unauthorized: Access denied to room xxxx
Instead of an name or service not known
Results of GitLab environment info
# gitlab-rake gitlab:env:info
System information
System: RedHatEnterpriseServer 6.9
Proxy: no
Current User: git
Using RVM: no
Ruby Version: 2.3.5p376
Gem Version: 2.6.13
Bundler Version:1.13.7
Rake Version: 12.0.0
Redis Version: 3.2.5
Git Version: 2.13.5
Sidekiq Version:5.0.4
Go Version: unknown
GitLab information
Version: 10.0.2-ee
Revision: f5b3271
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
DB Version: 9.6.3
URL: https://gitfqdn
HTTP Clone URL: https://gitfqdn/some-group/some-project.git
SSH Clone URL: git@gitfqdn:some-group/some-project.git
Elasticsearch: no
Geo: no
Using LDAP: yes
Using Omniauth: no
GitLab Shell
Version: 5.9.0
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
# gitlab-rake gitlab:check SANITIZE=true
Checking GitLab Shell ...
GitLab Shell version >= 5.9.0 ? ... OK (5.9.0)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
(REMOVED)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Reply by email is disabled in config/gitlab.yml
Checking LDAP ...
Server: ldapmain
not verifying SSL hostname of LDAPS server 'myldap:636'
LDAP authentication... Success
LDAP users with access to your GitLab server (only showing the first 100 results)
(REMOVED)
Checking LDAP ... Finished
Checking GitLab ...
Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... 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
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: ...
(REMOVED)
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.3 ? ... yes (2.3.5)
Git version >= 2.7.3 ? ... yes (2.13.5)
Git user has default SSH configuration? ... no
T(REMOVED)
Active users: ... (REMOVED)
Elasticsearch version 5.1 - 5.5? ... skipped (elasticsearch is disabled)
Checking GitLab ... Finished
/label ~bug