Replace SLES SMT Server
Closes gitlab-org/distribution/team-tasks#600 (closed)
Summary
This MR includes a change in the build environment for SLES 12.2, and the testing we've done confirms that:
- The new SMT server is serving packages as expected, and
- The repositories referenced in the Dockerfile that have replaced older, inaccessible repositories are functioning as expected
Testing
The examples below show testing that came from deploying the generated GitLab RPM for SLES 12.2 on a testing instance.
Note: we also attempted to run gitlab-qa against the instance, but had trouble finding the associated Docker image to use. The tests ran, but as expected, we saw many failures since the tests didn't align with the version of GitLab we deployed. We opened an issue to track this: omnibus-gitlab#5369 (closed)
gitlab-ctl status
mitchellnielsen@mitch-test-sles:~> sudo gitlab-ctl status
run: alertmanager: (pid 17473) 3587s; run: log: (pid 16168) 3771s
run: gitaly: (pid 17451) 3590s; run: log: (pid 13877) 3904s
run: gitlab-exporter: (pid 17437) 3590s; run: log: (pid 15870) 3793s
run: gitlab-workhorse: (pid 17414) 3593s; run: log: (pid 14727) 3819s
run: grafana: (pid 17488) 3586s; run: log: (pid 17345) 3613s
run: logrotate: (pid 22458) 208s; run: log: (pid 15809) 3806s
run: nginx: (pid 15290) 3816s; run: log: (pid 15684) 3813s
run: node-exporter: (pid 17422) 3592s; run: log: (pid 15845) 3799s
run: postgres-exporter: (pid 17481) 3586s; run: log: (pid 16639) 3760s
run: postgresql: (pid 14000) 3896s; run: log: (pid 14012) 3893s
run: prometheus: (pid 17445) 3590s; run: log: (pid 15920) 3781s
run: puma: (pid 14341) 3835s; run: log: (pid 14350) 3832s
run: redis: (pid 13788) 3913s; run: log: (pid 13796) 3910s
run: redis-exporter: (pid 17439) 3590s; run: log: (pid 15899) 3787s
run: sidekiq: (pid 14360) 3829s; run: log: (pid 14373) 3826sScreenshot of admin area
Screenshot of repo with changes made via SSH
Edited by Mitchell Nielsen