2025-01-23: All traffic dropped to redis-cluster-chat-cache
📝 Summary for CMOC notice / Exec summary:
- Customer Impact: None.
- Service Impact: ServiceRedisClusterChatCache
- Impact Duration: 1600 - 1730 (90 minutes)
- Root cause: RootCauseKnown-Software-Issue
Customer Impact
There was a recently merged changed that caused Duo Chat to not utilize a redis cache. The feature not using the cache should not impact the availability of Duo Chat or Duo Workflow, so there should be no observable customer impact.
Current Status
We are rolling back to an earlier deployment for which Duo Chat still uses the redis cache.
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 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.