[08/17/2022 - 00:00 UTC] - Patroni Clusters OS Upgrade - GSTG - Final
Production Change
Change Summary
gstg
environment.
Final Round of the Patroni OS Upgrade and Rollback maintenance on The Patroni Main
and CI
database clusters currently run on Ubuntu 16.04, an outdated Operating System. During this maintenance we will be promoting a new standby cluster for each Database which runs on Ubuntu 20.04 and update the Consul service registration to point Gitlab.com applications to the corresponding new Patroni clusters.
Key Benefits:
- Up to date operating system will provide increased security and stability.
- Install PostgreSQL packages from the upstream repositories supported by the Postgres development community.
Downtime Requirements:
Changes to the glibc
libraries from Ubuntu 16.04 to Ubuntu 18.10 and above lead to index corruption for PostgreSQL databases as discussed on https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/13273#note_566890549 . Due to this we need to reindex multiple indexes that have been detected as corrupted, which requires downtime.
OS Upgrade Rollout Team
Role | Assigned To |
---|---|
|
@gsgl |
|
@mchacon3 |
|
@dawsmith |
|
@bshah11 |
|
@gsgl |
|
@cheryl.li @mksionek |
|
N/A |
|
@devin |
|
@dawsmith |
Change Details
- Services Impacted - ServicePatroni ServicePatroniCI ServiceWeb ServiceAPI ServiceContainer Registry ServiceFrontend ServiceGit ServiceGitLab Rails ServiceGitLab SSHD ServiceSidekiq ServiceWorkhorse
-
Change Technician -
@mchacon3
- Change Reviewer - @ahanselka @gsgl @kwanyangu @Finotto @bshah11 @rhenchen.gitlab @alexander-sosna @dawsmith
- Time tracking - 180 minutes
- Downtime Component - YES
- Planned Start Time - Tuesday, 2022-08-17, 00:00 UTC
- Planned End Time - Tuesday, 2022-08-17, 03:00 UTC
Detailed steps for the change
Change Steps - steps to take to execute the change
This CR is for staging, however to follow the same process as we would for production, we will pretend that GitLab.com would be unavailable during the execution of the CR and we'll use ops.gitlab.net for the detailed instructions issue:
Change Reviewer checklist
-
Check if the following applies: - The scheduled day and time of execution of the change is appropriate.
- The change plan is technically accurate.
- The change plan includes estimated timing values based on previous testing.
- The change plan includes a viable rollback plan.
- The specified metrics/monitoring dashboards provide sufficient visibility for the change.
-
Check if the following applies: - The complexity of the plan is appropriate for the corresponding risk of the change. (i.e. the plan contains clear details).
- The change plan includes success measures for all steps/milestones during the execution.
- The change adequately minimizes risk within the environment/service.
- The performance implications of executing the change are well-understood and documented.
- The specified metrics/monitoring dashboards provide sufficient visibility for the change.
- If not, is it possible (or necessary) to make changes to observability platforms for added visibility?
- The change has a primary and secondary SRE with knowledge of the details available during the change window.
- The labels blocks deployments and/or blocks feature-flags are applied as necessary
Change Technician checklist
-
Check if all items below are complete: - The change plan is technically accurate.
- This Change Issue is linked to the appropriate Issue and/or Epic
- Change has been tested in staging and results noted in a comment on this issue.
- A dry-run has been conducted and results noted in a comment on this issue.
- For C1 and C2 change issues, the change event is added to the GitLab Production calendar.
- For C1 and C2 change issues, the SRE on-call has been informed prior to change being rolled out. (In #production channel, mention
@sre-oncall
and this issue and await their acknowledgement.) - For C1 and C2 change issues, the SRE on-call provided approval with the eoc_approved label on the issue.
- For C1 and C2 change issues, the Infrastructure Manager provided approval with the manager_approved label on the issue.
- Release managers have been informed (If needed! Cases include DB change) prior to change being rolled out. (In #production channel, mention
@release-managers
and this issue and await their acknowledgment.) - There are currently no active incidents that are severity1 or severity2
- If the change involves doing maintenance on a database host, an appropriate silence targeting the host(s) should be added for the duration of the change.