Mattermost Nginx IP address not updated on gitlab-ctl reconfigure.
Summary
gitlab-mattermost-http-conf listen address not being updated by chef after modifying gitlab.rb.
Steps to reproduce
- Update variable in gitlab.rb, then run gitlab-ctl update the configuration files.
nginx['listen_addresses'] = ['10.0.0.101']
Result.
gitlab-http.conf is updated correctly. server { listen 10.0.0.101:80;
gitlab-mattermost-http.conf is not updated. server { listen *:80;
System information: System: Ubuntu 16.04 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 Revision: 06a5a33 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql URL: http://gits.littleville.com HTTP Clone URL: http://gits.littleville.com/some-group/some-project.git SSH Clone URL: git@gits.littleville.com:some-group/some-project.git Using LDAP: no 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
Expected behavior
gitlab-mattermost-http.conf is updated with a sweet single ip address, so that I can run gitlab/mattermost on a second interface on the server without it interfering with other services running on the box.
server { listen 10.0.0.101:80;
Observed behavior
gitlab-mattermost-http.conf is not updated and remains the default. Updating it by hand works just fine, but is a bit of a problem when I upgrade/reconfigure.
Possible fixes
I don't see anything obvious in the chef recipes (compared to nginx-gitlab-http.conf.erb), but I'm far from a chef expert :)