2022-12-13: Update server ssl cert for DR archive postgres servers in staging

Staging DR Archive Database Change

Change Summary

This is to update server ssl certs for postgres by updating gitlab omnibus configurations on staging. Although server certificate already is the same as we want it to be but this CR will confirm the procedure, involving postgresql process restart to proceed with similar change changes in Production.

Reference issue: https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/16054

Change Details

1. Services Impacted - ServicePostgres
2. Change Technician - @fshabir
3. Change Reviewer - @rhenchen.gitlab
4. Time tracking - 60 minutes minutes
5. Downtime Component - YES Postgres will be restarted after adding new ssl certs on DR archive database servers in staging

Detailed steps for the change

Change Steps - steps to take to execute the change

Estimated Time to Complete (mins) - Estimated Time to Complete in Minutes

• Set label changein-progress /label ~change::in-progress
• Merge this MR: https://gitlab.com/gitlab-com/gl-infra/chef-repo/-/merge_requests/2650
• Run chef-client and omnibus-reconfigure on postgres-dr-archive-2004-01-db-gstg.c.gitlab-staging-1.internal

bundle exec knife ssh postgres-dr-archive-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo chef-client"
bundle exec knife ssh postgres-dr-archive-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl reconfigure"

• Restart postgres and check its status afterward to ensure its running. Observe any deviation in archive server activity for 5 minutes. Monitoring Dashboard

bundle exec knife ssh postgres-dr-archive-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl restart postgresql"
bundle exec knife ssh postgres-dr-archive-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl status postgresql"

• Run chef-client and omnibus-reconfigure on postgres-dr-delayed-2004-01-db-gstg.c.gitlab-staging-1.internal

bundle exec knife ssh postgres-dr-delayed-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo chef-client"
bundle exec knife ssh postgres-dr-delayed-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl reconfigure"

• Restart postgres and check its status afterward to ensure its running. Observe any deviation in archive server activity for 5 minutes. Monitoring Dashboard

bundle exec knife ssh postgres-dr-delayed-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl restart postgresql"
bundle exec knife ssh postgres-dr-delayed-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl status postgresql"

• Run chef-client and omnibus-reconfigure on postgres-ci-dr-archive-2004-01-db-gstg.c.gitlab-staging-1.internal

bundle exec knife ssh postgres-ci-dr-archive-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo chef-client"
bundle exec knife ssh postgres-ci-dr-archive-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl reconfigure"

• Restart postgres and check its status afterward to ensure its running. Observe any deviation in archive server activity for 5 minutes. Monitoring Dashboard

bundle exec knife ssh postgres-ci-dr-archive-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl restart postgresql"
bundle exec knife ssh postgres-ci-dr-archive-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl status postgresql"

• Run chef-client and omnibus-reconfigure on postgres-ci-dr-delayed-2004-01-db-gstg.c.gitlab-staging-1.internal

bundle exec knife ssh postgres-ci-dr-delayed-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo chef-client"
bundle exec knife ssh postgres-ci-dr-delayed-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl reconfigure"

• Restart postgres and check its status afterward to ensure its running. Observe any deviation in archive server activity for 5 minutes. Monitoring Dashboard

bundle exec knife ssh postgres-ci-dr-delayed-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl restart postgresql"
bundle exec knife ssh postgres-ci-dr-delayed-2004-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl status postgresql"

• Run chef-client and omnibus-reconfigure on postgres-registry-dr-archive-01-db-gstg.c.gitlab-staging-1.internal

bundle exec knife ssh postgres-registry-dr-archive-01-db-gstg.c.gitlab-staging-1.internal "sudo chef-client"
bundle exec knife ssh postgres-registry-dr-archive-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl reconfigure"

• Restart postgres and check its status afterward to ensure its running. Observe any deviation in archive server activity for 5 minutes. Monitoring Dashboard

bundle exec knife ssh postgres-registry-dr-archive-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl restart postgresql"
bundle exec knife ssh postgres-registry-dr-archive-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl status postgresql"

• Run chef-client and omnibus-reconfigure on postgres-registry-dr-delayed-01-db-gstg.c.gitlab-staging-1.internal

bundle exec knife ssh postgres-registry-dr-delayed-01-db-gstg.c.gitlab-staging-1.internal "sudo chef-client"
bundle exec knife ssh postgres-registry-dr-delayed-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl reconfigure"

• Restart postgres and check its status afterward to ensure its running. Observe any deviation in archive server activity for 5 minutes. Monitoring Dashboard

bundle exec knife ssh postgres-registry-dr-delayed-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl restart postgresql"
bundle exec knife ssh postgres-registry-dr-delayed-01-db-gstg.c.gitlab-staging-1.internal "sudo gitlab-ctl status postgresql"

• Set label changecomplete /label ~change::complete

Rollback

Rollback steps - steps to be taken in the event of a need to rollback this change

Estimated Time to Complete (mins) - 60 minutes

• Revert this MR: https://gitlab.com/gitlab-com/gl-infra/chef-repo/-/merge_requests/2650
• Run chef-client on each of DR archive servers, followed by omnibus-reconfigure and restart of postgresql

postgres-ci-dr-archive-2004-01-db-gstg.c.gitlab-staging-1.internal
postgres-ci-dr-delayed-2004-01-db-gstg.c.gitlab-staging-1.internal
postgres-dr-archive-2004-01-db-gstg.c.gitlab-staging-1.internal
postgres-dr-delayed-2004-01-db-gstg.c.gitlab-staging-1.internal
postgres-registry-dr-archive-01-db-gstg.c.gitlab-staging-1.internal
postgres-registry-dr-delayed-01-db-gstg.c.gitlab-staging-1.internal

• Set label changeaborted /label ~change::aborted

Monitoring

Key metrics to observe

• Metric: postgres-archive Service Error Ratio
  • Location: https://dashboards.gitlab.net/d/postgres-archive-main/postgres-archive-overview?orgId=1&viewPanel=3070963093&var-PROMETHEUS_DS=Global&var-environment=gstg&var-stage=main
  • What changes to this metric should prompt a rollback: Non-zero value in error ratio or an increase from pervious values after the CR
• Metric: transactions SLI Error Ratio
  • Location: https://dashboards.gitlab.net/d/postgres-archive-main/postgres-archive-overview?orgId=1&viewPanel=182327166&var-PROMETHEUS_DS=Global&var-environment=gstg&var-stage=main
  • What changes to this metric should prompt a rollback: Non-zero value in error ratio or an increase from pervious values after the CR

Change Reviewer checklist

C4 C3 C2 C1:

• 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.

C2 C1:

• 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.
  • The change execution window respects the Production Change Lock periods.
  • 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.