2021-07-28 Error 500 loading pages due to SQL mismatch in members table
Current Status
After package 14.2.202107280320-ea1185e2e8e.64918f4aeba
was deployed to Canary and database migrations were performed we started to see some 500 errors on the main Web fleet. Because of the mismatch in schema, it was necessary to HUP (restart) puma to reload the schema and resolved the errors.
This was a repeat of a similar issue #5171 (closed) .
During the incident we discovered that we need to improve some of our tooling around quickly issuing restarts to the deployed fleet, these improvements will be added to the list of corrective actions.
- Customer Impact: ServiceWeb ServiceAPI
- Customer Impact Duration: 06:30 - 12:00 5h30m
- Current state: See
Incident::<state>
label - Root cause: RootCauseSoftware-Change
Timeline
View recent production deployment and configuration events / gcp events (internal only)
All times UTC.
2021-07-28
-
07:36
- @stanhu declares incident in Slack.
Corrective Actions
Corrective actions should be put here as soon as an incident is mitigated, ensure that all corrective actions mentioned in the notes below are included.
- Add more safety to the deploycmd for fleet hup'ing https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/13885
- Setup a mixed deployment test environment
- Create ability to restart puma on Kubernetes deployed services
Note: In some cases we need to redact information from public view. We only do this in a limited number of documented cases. This might include the summary, timeline or any other bits of information, laid out in out handbook page. Any of this confidential data will be in a linked issue, only visible internally. By default, all information we can share, will be public, in accordance to our transparency value.
Click to expand or collapse the Incident Review section.
Incident Review
Summary
- Service(s) affected:
- Team attribution:
- Time to detection:
- Minutes downtime or degradation:
Metrics
Customer Impact
-
Who was impacted by this incident? (i.e. external customers, internal customers)
- ...
-
What was the customer experience during the incident? (i.e. preventing them from doing X, incorrect display of Y, ...)
- ...
-
How many customers were affected?
- ...
-
If a precise customer impact number is unknown, what is the estimated impact (number and ratio of failed requests, amount of traffic drop, ...)?
- ...
What were the root causes?
- ...
Incident Response Analysis
-
How was the incident detected?
- ...
-
How could detection time be improved?
- ...
-
How was the root cause diagnosed?
- ...
-
How could time to diagnosis be improved?
- ...
-
How did we reach the point where we knew how to mitigate the impact?
- ...
-
How could time to mitigation be improved?
- ...
-
What went well?
- ...
Post Incident Analysis
-
Did we have other events in the past with the same root cause?
- ...
-
Do we have existing backlog items that would've prevented or greatly reduced the impact of this incident?
- ...
-
Was this incident triggered by a change (deployment of code or change to infrastructure)? If yes, link the issue.
- ...
Lessons Learned
- ...
Guidelines
Resources
- If the Situation Zoom room was utilised, recording will be automatically uploaded to Incident room Google Drive folder (private)