2022-05-31: Roll out a fix for tag index page
Production Change
Change Summary
This change is related to rolling out fix_release_path_in_tag_index_page
to production.
The feature flag toggles a fix in the path for releases associated with a tag in the tag index page. This issue was created because the feature introduced by this flag had previously resulted in a production incident.
For more information, please check the rollout issue and the original issue for the fix.
This change is scheduled to be carried out tomorrow (June, 1st) starting at 08:30 UTC.
Change Details
- Services Impacted - ServiceGitLab Rails
-
Change Technician -
@ahmed.hemdan
- Change Reviewer - @gl-infra-danger-bot
- Time tracking - unknown
- Downtime Component - none
Detailed steps for the change
Change Steps - steps to take to execute the change
Estimated Time to Complete (mins) - 60-90 minutes (to have enough time to monitor the gradual roll out)
-
Set label changein-progress /label ~change::in-progress
-
Roll out feature to 25% of actors -
Roll out feature to 50% of actors -
Roll out feature to 75% of actors -
Roll out feature to 100% of actors -
Roll out feature globally on production -
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) - 3-5 minutes
-
Disable feature flag globally on production -
Set label changeaborted /label ~change::aborted
Monitoring
Key metrics to observe
- Metric: Metric Name
- Location: Dashboard URL
- What changes to this metric should prompt a rollback: Describe Changes
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 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.) - 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.
Edited by Ahmed Hemdan