Prometheus URL (port 9090) throws connection refused error after upgrade to 8.17.2
Summary
After upgrading from Gitlab CE 8.16.6 to CE 8.17.2 on a Centos 6 machine, the Prometheus url link (http://gitlab-server.domain.com:9090) began throwing a "Site can't be reached" error (ERR_CONNECTION_REFUSED). Running "gitlab-ctl status" shows that prometheus is up and running, and the prometheus, nginx, and gitlab logs are not reporting any errors. My guess is that the upgrade deleted a prometheus nginx web config file and I am unable to get Gitlab to recreate it.
Restarting Gitlab, retrying "gitlab-ctl reconfigure" and rebooting the server do not change anything. There is no firewall active, either. The only thing that seems to be missing is any nginx configuration file that opens port 9090.
Steps to reproduce
Have Gitlab CE 8.16.6 (with 8.17 gitlab.rb file that was accidentally grabbed instead of an 8.16 one) and then perform an omnibus upgrade to 8.17.2. When the upgrade is complete, refresh the prometheus link and it will show a "site can't be reached" error.
What is the current bug behavior?
Prometheus url link is down. No errors in the logs and it is assumed that a prometheus.conf nginx file is missing (no config file with port 9090 mentioned was found in /var/opt/gitlab/nginx/conf).
What is the expected correct behavior?
The Prometheus url should be up and active post-upgrade.
Results of GitLab environment info
System information
System: CentOS 6.6
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
Revision: bab14bdb
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: https://gitlab-server.domain.com
HTTP Clone URL: https://gitlab-server.domain.com/some-group/some-project.git
SSH Clone URL: git@gitlab-server.domain.com:some-group/some-project.git
Using LDAP: yes
Using Omniauth: no
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
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: ...
2/1 ... ok
4/2 ... ok
2/5 ... ok
2/6 ... ok
2/7 ... ok
2/8 ... ok
8/9 ... ok
8/10 ... repository is empty
8/11 ... ok
8/12 ... 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 ...
Server: ldapmain
LDAP authentication... Success
LDAP users with access to your GitLab server (only showing the first 100 results)
[redacted]
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? ... skipped (no tmp uploads folder yet)
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: ...
2/1 ... yes
4/2 ... yes
2/5 ... yes
2/6 ... yes
2/7 ... yes
2/8 ... yes
8/9 ... yes
8/10 ... yes
8/11 ... yes
8/12 ... 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: 7
Checking GitLab ... Finished
Possible fixes
Make sure that if prometheus is enabled and it has no nginx or web config file, that file is recreated.