# Production Change ## Change Summary Upgrades macOS production runners to runner version 19.1.0~pre.1227.g817ab3ac-1 and upgrades the host machine AMIs and macos-15/26 job images. MRs to be approved and merged before rollout: - [x] https://gitlab.com/gitlab-com/gl-infra/chef-repo/-/merge_requests/7518+ - [x] https://ops.gitlab.net/gitlab-com/gl-infra/config-mgmt/-/merge_requests/14453 Summary of changes: - Runner 19.1.0~pre.1227.g817ab3ac-1 also includes fixes for FF_LOG_IMAGES_CONFIGURED_FOR_JOB so we can visualize macOS job images in use. - New AMI includes some keychain unlock improvements and base OS updates - https://gitlab.com/gitlab-org/ci-cd/shared-runners/images/aws/macos-nesting/-/merge_requests/78+ - Job images include runner v19 helper image, fixing cache flag compatibility with v19 runner managers - https://gitlab.com/gitlab-com/gl-infra/production-engineering/-/work_items/29091+ The macOS runner shards/deployments to be updated and started (see [current active colours here](https://dashboards.gitlab.net/d/ci-runners-deployment/ci-runners3a-deployment-overview?from=now-15m&orgId=1&timezone=utc&to=now&var-PROMETHEUS_DS=mimir-gitlab-gprd&var-environment=gprd&var-project_jobs_running=$__all&var-runner_job_failure_reason=$__all&var-shard=saas-macos-medium-m1&var-shard=saas-macos-large-m2pro&var-stage=main&var-type=ci-runners&viewPanel=panel-16)): - saas-macos-medium-m1/blue - saas-macos-large-m2pro/green **NB**: This change runs at the weekend as this is the only time where we have enough dedicated host capacity to handle the switchover. There is minimal macOS capacity in US zones to acquire new machines on demand. ## Change Details 1. **Services Impacted** - ~"Service::CI Runners" 1. **Change Technician** - `@joe-shaw` 1. **Change Reviewer** - @rehab 1. **Scheduled Date and Time (UTC in format YYYY-MM-DD HH:MM)** - 2026-06-20 21:00 1. **Time tracking** - 60 minutes 1. **Downtime Component** - none > [!IMPORTANT] > If your change involves scheduled maintenance, add a step to set and > [unset maintenance mode](https://gitlab.com/gitlab-com/runbooks/-/blob/master/docs/monitoring/set_maintenance_window.md) > per our runbooks. This will make sure SLA calculations adjust for the maintenance period. ## Preparation > [!NOTE] > The following checklists must be done in advance, before setting the label ~"change::scheduled" ### Change Reviewer checklist ~C4 ~C3 ~C2 ~C1: - [x] Check if the following applies: - The **scheduled day and time** of execution of the change is appropriate. - The [change plan](#detailed-steps-for-the-change) is technically accurate. - The change plan includes **estimated timing values** based on previous testing. - The change plan includes a viable [rollback plan](#rollback). - The specified [metrics/monitoring dashboards](#key-metrics-to-observe) 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 change window has been agreed with Release Managers in advance of the change. If the change is planned for APAC hours, this issue has an agreed pre-change approval. - The labels ~"blocks deployments" and/or ~"blocks feature-flags" are applied as necessary. ### Change Technician checklist - [x] The [Change Criticality](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#change-criticalities) has been set appropriately and requirements have been reviewed. - [x] The [change plan](#detailed-steps-for-the-change) is technically accurate. - [x] The [rollback plan](#rollback) is technically accurate and detailed enough to be executed by anyone with access. - [x] This Change Issue is linked to the appropriate Issue and/or Epic - [x] Change has been tested in staging and results noted in a comment on this issue. - [x] A dry-run has been conducted and results noted in a comment on this issue. - [x] The change execution window respects the [Production Change Lock periods](https://about.gitlab.com/handbook/engineering/infrastructure/change-management/#production-change-lock-pcl). - [x] Once all boxes above are checked, mark the change request as scheduled: `/label ~"change::scheduled"` - [ ] For ~C1 and ~C2 change issues, the change event is added to the [GitLab Production](https://calendar.google.com/calendar/embed?src=gitlab.com_si2ach70eb1j65cnu040m3alq0%40group.calendar.google.com) calendar by the [change-scheduler bot](https://gitlab.com/gitlab-com/gl-infra/ops-team/toolkit/change-scheduler). It is schedule to run every 2 hours. - [ ] For ~C1 and ~C2 change issues, Platform Leadership provides approval with the ~platform_leadership_approved label on the issue. Mention `@gitlab-org/saas-platforms/change-review-leadership` in this issue with a reference to [review guidelines](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/platform-leadership-review/) to get approval and provide visibility to all infrastructure managers. - [ ] For ~C1, ~C2, or ~"blocks deployments" change issues, confirm with Release managers that the change does not overlap or hinder any release process (In `#production` channel, mention `@release-managers` and this issue and await their acknowledgment.) - [ ] For ~C1 change issues or ~C2 change issues happening during weekend, SREs on-call must be informed [at least 2 weeks in advance](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#approval). Check [the incident.io GitLab.com Production EOC schedule](https://app.incident.io/gitlab/on-call/schedules/01K5YWAGZ7YCQGAG7ATQ9XQWHW) to find who will be on-call at the scheduled day and time. ## Detailed steps for the change ### Pre-execution steps > [!NOTE] > The following steps should be done right at the scheduled time of the change request. The [preparation steps](#preparation) are > listed below. - [x] Make sure all tasks in [Change Technician checklist](#change-technician-checklist) are done - [ ] For ~C1 and ~C2 change issues, the SRE on-call has been informed prior to change being rolled out. - [ ] The SRE on-call provided approval with the ~eoc_approved label on the issue. - [ ] For ~C1, ~C2, or ~"blocks deployments" change issues, Release managers have been informed prior to change being rolled out. (In `#production` channel, mention `@release-managers` and this issue and await their acknowledgment.) - [x] There are currently no [active incidents](https://gitlab.com/gitlab-com/gl-infra/production/-/issues/?sort=created_date&state=opened&label_name%5B%5D=Incident%3A%3AActive&or%5Blabel_name%5D%5B%5D=severity%3A%3A1&or%5Blabel_name%5D%5B%5D=severity%3A%3A2&first_page_size=20) that are ~severity::1 or ~severity::2 - [ ] 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. ### Change steps - steps to take to execute the change *Estimated Time to Complete (mins)* - 60 - [x] Set label ~"change::in-progress" `/label ~change::in-progress` * [x] Confirm that [`19.1.0~pre.1227.g817ab3ac-1`](https://packages.gitlab.com/ui/browse/runner/unstable/debian/pool/main/g/gitlab-runner) is published * [x] Log into the respective [AWS environments](https://runbooks.gitlab.com/ci-runners/macos/#environments) and check that there are enough dedicated hosts available to scale into. The hosts should show no utilisation, but be ready for use. * You should already have access to the AWS account for macOS runners: navigate to `us-east-1` -> `EC2` -> `Dedicated Hosts`. There should be at least 4 "empty" hosts there ready to be used. * [x] Check that the inactive deployment colors still match expectations before moving forward. * [x] Ensure that latest macOS host AMIs have been published to production accounts - https://gitlab.com/gitlab-org/ci-cd/shared-runners/images/aws/macos-nesting/-/pipelines/2546137382 * [x] Start `saas-macos-large-m2pro/green` via `#production`: ``` /runner run start saas-macos-large-m2pro green ``` * [x] Start `saas-macos-medium-m1/blue` via `#production`: ``` /runner run start saas-macos-medium-m1 blue ``` * [x] Wait for first jobs to be taken up by the newly started runner managers - this can take 20+ minutes due to provisioning and VM download times. * [x] Verify macOS production test pipelines are fully functional - https://gitlab.com/gitlab-org/ci-cd/tests/saas-runners-tests/macos-platform/saas-macos-production-tests - ensure new colors are visibly picking up jobs. * [x] Stop `saas-macos-large-m2pro/blue` via `#production`: ``` /runner run stop saas-macos-large-m2pro blue ``` * [x] Stop `saas-macos-medium-m1/green` via `#production`: ``` /runner run stop saas-macos-medium-m1 green ``` - [x] Set label ~"change::complete" `/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 * [ ] Start `saas-macos-large-m2pro/blue` via `#production`: ``` /runner run start saas-macos-large-m2pro blue ``` * [ ] Start `saas-macos-medium-m1/green` via `#production`: ``` /runner run start saas-macos-medium-m1 green ``` * [ ] Wait for first jobs to be taken up by the newly started runner managers * [ ] Stop `saas-macos-large-m2pro/green` via `#production`: ``` /runner run stop saas-macos-large-m2pro green ``` * [ ] Stop `saas-macos-medium-m1/blue` via `#production`: ``` /runner run stop saas-macos-medium-m1 blue ``` * [ ] Revert MRs: * [ ] https://gitlab.com/gitlab-com/gl-infra/chef-repo/-/merge_requests/7518 * [ ] https://ops.gitlab.net/gitlab-com/gl-infra/config-mgmt/-/merge_requests/14453 - [ ] Set label ~"change::aborted" `/label ~change::aborted` ## Monitoring ### Key metrics to observe Filter following queries to the relevant macOS runner shards. Metric: Runners Deployment status * Location: https://dashboards.gitlab.net/goto/PD29_t8Hg?orgId=1 * What changes to this metric should prompt a rollback: increased failure on jobs or drop in processed jobs. Logs: Runner Index * Location: https://log.gprd.gitlab.net/app/r/s/vuVXu * What changes should prompt a rollback: An unrecoverable system error that prevents the runner-managers from creating new dedicated hosts. Metric: CI Runners Overview * Location: https://dashboards.gitlab.net/goto/DZ2eltUNg?orgId=1 * What changes to this metric should prompt a rollback: A drop in the runner's Apdex or an increase in Error ratios. Metric: Incident Support: Runner Manager * Location: https://dashboards.gitlab.net/goto/fapRutUNR?orgId=1 * What changes to this metric should prompt a rollback: Unexpected change in any of the metrics. Metric: Executed jobs by shard * Location: https://dashboards.gitlab.net/goto/Rt3Wut8NR?orgId=1 * What changes to this metric should prompt a rollback: Drop in the executed jobs by both deployment color.