2023-07-13: [CNY] GitServiceGitlabSshdApdexSLOViolation
Customer Impact
Slow queries for git ops over ssh affecting <5% of the requests, due to the incident being restricted to our canary fleet. No actual customer reports about slowness at this point.
Current Status
Following the deployment of 16.2.202307131100-130de824047.b1dfe4369df
, we saw a git Apdex dip, due to spike in sshd latency:
ref: https://dashboards.gitlab.net/goto/CipkYdCVg?orgId=1
We're continuing to look into the root cause, after we drained CNY.
Since CNY is drained and no longer receiving requests the problem should no longer occur for now. We do not put the incident into mitigated since we're still exploring and cannot yet unblock further deploys.
We are reverting the gitlab-shell version bump that likely caused this incident in gitlab-org/gitlab!126334 (merged). Still
More information will be added as we investigate the issue. For customers believed to be affected by this incident, please subscribe to this issue or monitor our status page for further updates. If after a revert and a deploy to CNY we see the same latency spike in the p90 gitlab_sshd , we should look into the changes in gitlab:
📝 Summary for CMOC notice / Exec summary:
- Customer Impact: slow queries for git ops over ssh affecting <5% of the requests.
- Service Impact: ServiceGit ServiceGitlab Shell ServiceGitLab SSHD
- Impact Duration: 13:20 UTC - 14:09 UTC (30m)
- Root cause: RootCauseSoftware-Change
📚 References and helpful links
Recent Events (available internally only):
- Feature Flag Log - Chatops to toggle Feature Flags Documentation
- Infrastructure Configurations
- GCP Events (e.g. host failure)
Deployment Guidance
- Deployments Log | Gitlab.com Latest Updates
- Reach out to Release Managers for S1/S2 incidents to discuss Rollbacks, Hot Patching or speeding up deployments. | Rollback Runbook | Hot Patch Runbook
Use the following links to create related issues to this incident if additional work needs to be completed after it is resolved:
- Corrective action ❙ Infradev
- Incident Review ❙ Infra investigation followup
- Confidential Support contact ❙ QA investigation
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 our 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.