2023-04-26: gstg-cny-gitaly failing
Customer Impact
This was internal facing issue which blocked deployments to gstg-cny
.
Current Status
A configuration update of Gitaly resulted in leaving following gitaly servers in bad state in gstg-cny
:
- file-praefect-cny-01-stor-gstg.c.gitlab-staging-1.internal
- file-praefect-cny-02-stor-gstg.c.gitlab-staging-1.internal
- file-praefect-cny-03-stor-gstg.c.gitlab-staging-1.internal
gitlab-ctl reconfigure
couldn't be run on these servers due to conflicting configuration keys: (gitaly['storage']
vs gitaly['configuration']['storage']
)
Initially one of the conflicting key was removed from the servers manually and chef-client was disabled to avoid reverting the hotfix, to unblock deployments.
Subsequently, conflicting key was removed by updating chef role and a following chef-client run converged those servers to a good state with chef-client enabled.
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.