Corrective action: Staging returns 500 errors - document `chatops migration mark` in runbooks
Summary
During production#16894 (closed) we needed to mark a migration as completed even though it was failing, to enable future deployments to work.
This was done using the /chatops run migrations mark
command, as suggested by @stomlinson. Initially the response team had planned to do this via a change request (production#16895 (closed)).
We should document the usage of this command, which is much faster and efficient than using a CR.
Related Incident(s)
Originating issue(s): production#16894 (closed)
Desired Outcome/Acceptance Criteria
Document the usage of the /chatops run migrations mark
command in the appropriate runbook.
@amyphillips: Maybe https://gitlab.com/gitlab-com/runbooks#deploy would be the right place. I can't find anything existing (assuming I'm searching for the right terms)
Associated Services
Corrective Action Issue Checklist
-
Link the incident(s) this corrective action arose from -
Give context for what problem this corrective action is trying to prevent re-occurring -
Assign a severity label (this is the highest sev of related incidents, defaults to 'severity::4') -
Assign a priority (this will default to 'Reliability::P4' but should match the severity of the related incident) -
Assign a service label
Edited by François Rosé