2023-05-17: Expired certificate for int.gprd.gitlab.net
Customer Impact
Between 19:54 and 20:39 UTC - customers were not able to access any features that routed through our internal API
Status update 20:59 UTC
As of 20:39, the cert has been successfully updated and we have seen evidence of everything being operational. After a period of observation, we are confident that this issue has been resolved.
📝 Summary for CMOC notice / Exec summary:
- Customer Impact: Customers received errors when accessing features that used our internal API, such as merging MRs, web-IDE
- Service Impact: Internal API
- Impact Duration: 19:54 - 20:39
- Root cause: ~"RootCause::Infrastructure" RootCauseConfig-Change
Current Status
Received a blackbox alert regarding https://int.gprd.gitlab.net:11443/users/sign_in
Blackbox logs show the following failed probes for this domain:
Module | Target | Result | Debug |
---|---|---|---|
tls_expiry | int.gprd.gitlab.net:11443 | Failure | Logs |
http_2xx | https://int.gprd.gitlab.net:11443/-/liveness | Failure | Logs |
http_2xx | https://int.gprd.gitlab.net:11443/users/sign_in | Failure | Logs |
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.
📚 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 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.