Change Gitlab Shared Runners Managers to use new CI HAProxy fleet (try 2)
C3
Production Change - Criticality 3Change Objective | Change Gitlab Shared Runners Managers to use new CI HAProxy fleet (try 2) |
---|---|
Change Type | ConfigurationChange |
Services Impacted | ServiceCI Runners ServiceHAProxy |
Change Team Members | @T4cC0re |
Change Criticality | C3 |
Change Reviewer or tested in staging | was tested on staging environment |
Dry-run output | If the change is done through a script, it is mandatory to have a dry-run capability in the script, run the change in dry-run mode and output the result |
Due Date | 2020-05-28 14:30 UTC |
Time tracking | 45 minutes |
Detailed steps for the change
This change issue duplicates #2173 (closed) on purpose, as this is the second try after applying fixes to the cookbook.
-
Apply this MR: https://ops.gitlab.net/gitlab-cookbooks/chef-repo/-/merge_requests/3590 -
Ensure the configuration was written to the gitlab-shared-runners-managers -
When running a job on those gitlab shared runners (e.g. gitlab-org/gitlab) you should see something like this:
From https://ci-api.gprd.gitlab.net/this/is/the/repo
* [new ref] refs/pipelines/12776083 -> refs/pipelines/12776083
* [new branch] master -> origin/master
Checking out 6d58aea0 as master...
Rollback steps
Changes checklist
-
Detailed steps and rollback steps have been filled prior to commencing work -
SRE on-call has been informed prior to change being rolled out -
There are currently no open issues labeled as ServiceMonitoring with severities of ~S1 or ~S2
Edited by Hendrik Meyer (xLabber)