Provider
ClouderaIncident detail
FreeIPA clusters are in an unreachable state
Timeline window
to
Get alerted the next time Cloudera breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Investigating
Current Status: We are currently investigating a potential issue with the FreeIPA service.
Customer Experience: Customer may observe FreeIPA service in an unreachable status.
Investigating
We are continuing to investigate this issue.
Identified
Current Status: Our teams have identified the source of the issue.
We are working on developing and implementing a solution to restore the service(s).
We will have another update within 60 mins.
Customer Experience: Customer may observe FreeIPA service in an unreachable status.
Incident Start time: ~10:53 UTC Feburary 14th, 2024
Monitoring
Current Status: Our teams have identified the source of the issue and have implemented a solution which is under monitoring.
We will have another update within 60 mins.
Customer Experience: Customer may observe FreeIPA service in an unreachable status.
Incident Start time: ~10:53 UTC Feburary 14th, 2024
Resolved
Current Status: Our teams have confirmation that the solution implemented has addressed the issue. If you continue to experience issues please raise a support case with us.
A root cause analysis (RCA) will be published within seven business days.
Customer Experience: Customers may observe FreeIPA service in an unreachable status.
Incident Start time: ~10:53 UTC Feburary 14th, 2024
Resolved
On February 14, 2024, a scheduled monthly Kubernetes maintenance activity unintentionally caused a 30-minute outage for the FreeIPA service within the Control Plane. While the service itself remained functional on workloads, the issue stemmed from a bug introduced during the maintenance. This bug impacted the Inverting Proxy component, responsible for facilitating communication between the Control Plane and workloads, leading to the temporary disruption.
The team promptly identified and rectified the bug, restoring full service approximately within 30 minutes. Additionally, we have implemented corrective measures within the maintenance automation to prevent similar occurrences in the future.
We sincerely apologize for the inconvenience this incident may have caused.
Keep exploring
More from Cloudera
Neighboring incidents on Cloudera's timeline and the rest of their record on OutageDeck.