2024-04-04: two sidekiq pods in the urgent-cpu-bound shard are caught in a crashloop
Customer Impact
Current Status
2 of the Urgent CPU bound sidekiq Pods were crashlooping. A single pod was not reporting itself as ready despite having run for 39 hours. The pod was killed and the new pod came online and reported as ready resolving the incident.
NAME READY STATUS RESTARTS AGE
gitlab-sidekiq-urgent-cpu-bound-v2-7bb9999dc4-77vfd 1/1 Running 0 21m
gitlab-sidekiq-urgent-cpu-bound-v2-7bb9999dc4-d6r58 1/1 Running 0 123m
gitlab-sidekiq-urgent-cpu-bound-v2-7bb9999dc4-j59hr 0/1 CrashLoopBackOff 13 (4m8s ago) 47m
gitlab-sidekiq-urgent-cpu-bound-v2-7bb9999dc4-pcwvm 0/1 CrashLoopBackOff 11 (4m9s ago) 40m
gitlab-sidekiq-urgent-cpu-bound-v2-7bb9999dc4-srb6s 1/1 Running 0 47m
This was preventing gstg:auto-deploys
https://ops.gitlab.net/gitlab-com/gl-infra/k8s-workloads/gitlab-com/-/jobs/13416823
📚 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.
Security Note: If anything abnormal is found during the course of your investigation, please do not hesitate to contact security.