Change Request [PRDSUB] Run rake task `data_maintenance:subscriptions:bulk_update_price_change_option` on CustomersDot
Production Change
Change Summary
Related issue: https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/9244
Rake task introduced in: https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/9744
To be run in:
customers-01-inf-prdsub.c.gitlab-subscriptions-prod.internal
Prerequisites
- A CSV containing subscriptions to update. Can be obtained from @rcobb or @tgolubeva
CSV Format
subscription_id,charge_number
8a8aa16f8ecc4a8c018ecf70675e6e90,C-00215973
Running task
To run the task in dry run mode
bundle exec rake data_maintenance:subscriptions:bulk_update_price_change_option\['path/to/file.csv','UseLatestProductCatalogPricing','true'\]
To run the task
bundle exec rake data_maintenance:subscriptions:bulk_update_price_change_option\['path/to/file.csv','UseLatestProductCatalogPricing','false'\]
What does the rake task do?
Ingests CSV and updates included subscriptions rate plan charge price_change_option.
Change Details
- Services Impacted - ServiceCustomersDot
- Change Technician - @ahanselka
- Change Reviewer - @cmcfarland
- Time tracking - ~30 minutes
- Downtime Component - 0 minutes
Detailed steps for the change
Change Steps - steps to take to execute the change
Estimated Time to Complete (mins) - 30 minutes
-
Set label changein-progress /label ~change::in-progress
-
SCP eoa_price_change_option.csv
to production node/home/customersdot/CustomersDot/current/tmp
-
SSH to customerDot production ssh customers-01-inf-prdsub.c.gitlab-subscriptions-prod.internal
-
change user and navigate to current directory
sudo su - customersdot
cd /home/customersdot/CustomersDot/current
-
Run with dry run on RAILS_ENV=production bundle exec rake data_maintenance:subscriptions:bulk_update_price_change_option\['tmp/eoa_price_change_option.csv','UseLatestProductCatalogPricing','true'\]
-
Share output of task with @rcobb and @tgolubeva -
Run with dry run off RAILS_ENV=production bundle exec rake data_maintenance:subscriptions:bulk_update_price_change_option\['tmp/eoa_price_change_option.csv','UseLatestProductCatalogPricing','false'\]
-
Share output of task with @rcobb and @tgolubeva -
Set label changecomplete /label ~change::complete
Rollback
Rollback steps - steps to be taken in the event of a need to rollback this change
N/A
Monitoring
Key metrics to observe
Check subscriptions price_change_option has been updated
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 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
-
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 prior to any C1, C2, or blocks deployments 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 Alex Hanselka