Corrective action: Staging returns 500 errors - `ai_access_token` column migration
Summary
This MR gitlab-org/gitlab!132635 (merged) caused a sev-2 incident which as caught in staging: production#16894 (closed)
The same issue could impact self-managed customers that upgrade to %16.5. This should be corrected before the end of the 16.5 milestone.
Related Incident(s)
Originating issue(s): production#16894 (closed)
Desired Outcome/Acceptance Criteria
Observation during the incident response (slack)
wrong column name
encrypted_ prefix is missing
The application usesai_access_token
but the actual value is stored in theencrypted_ai_access_token
column.
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é