2024-04-17: The Disk Space Utilization per Device per Node resource of the ci-runners service (main stage) is on track to hit capacity within 6h
Customer Impact
None
Current Status
We've disabled debug logging, and the log rate is back to normal.
Summary
On 2024-04-16 an engineer enabled debug logging by updating the config.toml
with log_level = "debug"
to debug a production issue. Then they enabled chef-client
so that it removed the log_level = "debug"
, hoping log_level
will go back to info
. However we faced a bug in GitLab Runner config reloader which resulted in not updating the log_level
if it's not specified, so it never was updated from debug
to info
(default value) which resulted in the disk filling up.
We opened 2 infradev issues to fix these problems:
- Enable structured logging for taskscaler and fl... (gitlab-org/gitlab-runner#37489 - closed)
- Log level not updated when not specified (gitlab-org/gitlab-runner#37490)
📚 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.