2023-05-11 CustomersDot - Upgrade Ruby from 2 to 3

Production Change

Change Summary

Updating Ruby version from 2.7.8 to 3.2.2 in stgsub (staging) and prdsub (production) environments.

Change Details

1. Services Impacted - ServiceCustomersDot
2. Change Technician - @vitallium
3. Change Reviewer - @ebaque
4. Time tracking - 120
5. Downtime Component - none

Detailed steps for the change

Change Steps - steps to take to execute the change

Estimated Time to Complete (mins) - 30

• Set label changein-progress /label ~change::in-progress
• Create ~"production::blocker" issue in CustomerDot repo.
• Create a merge request for switching Ruby version from 2.7.8 to 3.2.2 in CustomersDot repo.
  • https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/7319+
• Create a merge request for updating Ruby version in the Ansible repo.
  • https://gitlab.com/gitlab-org/customersdot-ansible/-/merge_requests/425+
• Merge the first MR in CustomersDot repo in order to make the pipeline green in the Ansible repo.
• Restart the pipeline for the MR in the Ansible repo.
• Merge the MR in the Ansible repo.
• staging: Ensure Puma is working fine with systemctl status puma
• staging: Ensure Sidekiq is working fine with systemctl status sidekiq
• staging: Do smoke testing of following things:
  • Sign in via GitLab.com
  • Preview any purchase on GitLab.com
  • Preview any purchase on CustomersDot
  • Check the payment methods page renders payment methods.
• Remove the ~"production::blocker" label to deploy CustomersDot to production.
• Provision the production environment
• production: Ensure Puma is working fine with systemctl status puma
• production: Ensure Sidekiq is working fine with systemctl status sidekiq
• production: Do smoke testing of the following things:
  • Sign in via GitLab.com
  • Preview any purchase on GitLab.com
  • Preview any purchase on CustomersDot
  • Check the payment methods page renders payment methods.
• 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) - 20

• Create and merge an MR which swaps Ruby versions for CustomersDot repo.
• Create and merge an MR which swaps Ruby versions for the Ansible repo.
• Provision the production environment
• If required, cancel staging or production deployments job and start them manually.
• Ensure Puma is working fine with systemctl status puma
• Ensure Sidekiq is working fine with systemctl status sidekiq
• Do smoke testing of the following things:
  • Sign in via GitLab.com
  • Preview any purchase on GitLab.com
  • Preview any purchase on CustomersDot
  • Check the payment methods page renders payment methods.
• Set label changeaborted /label ~change::aborted

Monitoring

Key metrics to observe

• Metric: Puma

  • Location: https://dashboards.gitlab.net/d/customersdot-main/customersdot-overview?orgId=1
  • What changes to this metric should prompt a rollback: Puma reports an unrecoverable error or a Ruby error.

• Metric: Sidekiq

  • Location: https://dashboards.gitlab.net/d/customersdot-main/customersdot-overview?orgId=1
  • What changes to this metric should prompt a rollback: Sidekiq reports an unrecoverable error or a Ruby error.

• Metric: Health check

  • Location: https://customersdot.cloudwatch.net/dashboard
  • What changes to this metric should prompt a rollback: If both Puma and Sidekiq are running but we still receive health error.

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.