Historique des pannes de Cloudera

1. 3 septembre 2026 à 23:18 UTCinvestigating

   Nous enquêtons actuellement sur un problème potentiel d'accès à la console de gestion Cloudera. Une mise à jour sera fournie dans les 90 minutes. Expérience client: Le client peut observer Message d'erreur: "pas d'amont sain" tout en accédant à Cloudera Management Console.

2. 3 septembre 2026 à 23:18 UTCinvestigating

   Nous continuons d'enquêter sur cette question.

3. 4 septembre 2026 à 00:55 UTCinvestigating

   Statut actuel : Nos équipes étudient activement la cause profonde du problème. Nous prévoyons fournir une autre mise à jour dans les 90 minutes.

4. 4 septembre 2026 à 02:47 UTCresolved

   Situation actuelle : Nos équipes ont mis en œuvre avec succès une solution pour résoudre le problème. Nos équipes surveillent actuellement la solution et fourniront une autre mise à jour une fois confirmée. Expérience client : Le client peut avoir observé un message d'erreur : « pas de santé en amont » tout en accédant à Cloudera Management Console. Si vous rencontrez encore des problèmes ou avez des questions, s'il vous plaît soulever un cas de soutien avec nous. Une analyse des causes profondes sera publiée dans les sept jours ouvrables.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 11 mai 2026 à 18:12 UTCresolved

   Our teams have identified a potential performance issue on our US control plane. Our teams have successfully deployed a fix to address the issue. If you are still experiencing issues or have any questions, please raise a support case with us. A Root Cause Analysis (RCA) will be published within seven business days.

2. 22 mai 2026 à 19:29 UTCpostmortem

   On March 10, 2026, between 15:23 UTC to 17:09 UTC, users may have experienced intermittent connectivity issues accessing the workloads in the Cloudera Management Console of the US region. This disruption was traced to the termination of jumpgate-proxy pods, which entered an OOMKilled status after memory utilization exceeded configured limits. This, in turn, impacted connectivity between the control plane and the workloads within the Cloudera Management Console. Service consistency was restored by increasing the memory limits and replica counts for the jumpgate-proxy deployment. To prevent recurrence, we will implement alerting mechanisms for jumpgate pod memory utilization and pod states \(such as CrashLoopBackoff or OOMKilled events\). This will enable us to proactively detect and mitigate memory pressure before it impacts service availability. We will implement autoscaling to autoheal and respond to increased load. We sincerely apologise for any inconvenience this service disruption may have caused. We appreciate your patience as we worked to restore service functionality.

1. 18 mars 2026 à 22:03 UTCresolved

   Summary: On March 10, 2026, starting at around 19:56 UTC we experienced intermittent connectivity issues with the Cloudera Management Console and API across our US, EU, and AP regions. A root cause analysis (RCA) will be published within seven business days. Impact: Access to the administrative UI and API was affected; however, no data workloads or running environments were interrupted.

2. 18 mars 2026 à 22:07 UTCpostmortem

   On March 10, 2026, around 19:56 UTC users may have started experiencing intermittent timeouts accessing the Cloudera Management Console across the US, EU, and AP regions.  This disruption was traced to an internal service certificate expiration where, despite a successful renewal initiation, a misalignment in the deployment sequence prevented the updated credentials from propagating to the active service mesh. The impact was strictly limited to administrative console and API access; all existing data workloads and running environments continued to operate without interruption.  Service consistency was restored by regenerating and manually applying the certificates across all affected clusters. To prevent recurrence, we have audited all regional clusters and are transitioning to an automated lifecycle for mesh-level certificates.  We sincerely apologize for any inconvenience this service disruption may have caused. We are addressing monitoring gaps to detect these issues before they impact you, our customers. We appreciate your patience as we worked to restore service functionality.

1. 25 septembre 2025 à 10:23 UTCmonitoring

   Current Status: Our teams have identified the source of the issue and have implemented a solution which has fixed the issue. We are monitoring the situation. Customer Experience: During this window customers may experience issues accessing FreeIPA service

2. 25 septembre 2025 à 17:02 UTCresolved

   Our engineering teams have confirmed that the issues affecting the Management Console & FreeIPA services are now fully resolved, and all systems are confirmed to be operating normally. Should you continue to experience any trouble, please raise a support case with us. We sincerely apologise for any inconvenience this may have caused and we will have the root cause analysis (RCA) published within 7 business days.

3. 13 octobre 2025 à 20:04 UTCpostmortem

   The intermittent performance and access issues with the Cloudera Management Console and FreeIPA were triggered by a scheduled service upgrade intended to improve platform stability. Our investigation determined that a change in a core component introduced a latent configuration issue. This specific condition was not exposed in our testing environments, preventing dependent services from applying dynamic configuration updates in production and leading to the outage. We've taken immediate action to prevent this issue from recurring: System Fix: The problematic component change was rolled back, and a permanent patch was deployed to restore proper dynamic configuration functionality. Process Overhaul: We've implemented a more rigorous upgrade process with mandatory, near-production scale validation steps that specifically test for these types of configuration failures. Enhanced Monitoring: We significantly improved our monitoring and alerting capabilities to detect these abnormal service behaviours much earlier, ensuring a faster response time. We are dedicated to providing a reliable platform and will continue to invest in our infrastructure and processes. Thank you again for your patience and understanding

1. 24 septembre 2025 à 19:42 UTCinvestigating

   Current Status: We are currently investigating an issue causing intermittent performance and access problems for the Management Console. Our engineering teams are working to identify the root cause and restore full functionality. We will provide another update within the next 90 minutes. Customer Experience: Customers may experience intermittent performance degradation, slow load times, or errors when attempting to access the Management Console. Incident Start time: 19:13 UTC September 24th, 2025

2. 24 septembre 2025 à 20:53 UTCmonitoring

   *Current Status:* Our engineering teams have identified the likely root cause and have rolled out a fix. We are currently monitoring the system to confirm that this has resolved the performance and access issues for the Management Console. *Customer Experience:* Service availability and performance for the Management Console should now be returning to normal for all users. We will continue to monitor for any residual effects.

3. 25 septembre 2025 à 17:01 UTCresolved

   Our engineering teams have confirmed that the issues affecting the Management Console & FreeIPA services are now fully resolved, and all systems are confirmed to be operating normally. Should you continue to experience any trouble, please raise a support case with us. We sincerely apologise for any inconvenience this may have caused and we will have the root cause analysis (RCA) published within 7 business days.

4. 13 octobre 2025 à 20:02 UTCpostmortem

   The intermittent performance and access issues with the Cloudera Management Console and FreeIPA were triggered by a scheduled service upgrade intended to improve platform stability. Our investigation determined that a change in a core component introduced a latent configuration issue. This specific condition was not exposed in our testing environments, preventing dependent services from applying dynamic configuration updates in production and leading to the outage. We've taken immediate action to prevent this issue from recurring: System Fix: The problematic component change was rolled back, and a permanent patch was deployed to restore proper dynamic configuration functionality. Process Overhaul: We've implemented a more rigorous upgrade process with mandatory, near-production scale validation steps that specifically test for these types of configuration failures. Enhanced Monitoring: We significantly improved our monitoring and alerting capabilities to detect these abnormal service behaviours much earlier, ensuring a faster response time. We are dedicated to providing a reliable platform and will continue to invest in our infrastructure and processes. Thank you again for your patience and understanding

1. 13 août 2025 à 14:33 UTCinvestigating

   Current Status: We are currently investigating a potential issue with DataHubs, DataLakes and FreeIPA service across US region. We will have an update within 60 mins. Customer Experience: Customer may observe issues when access DataHubs, DataLakes and FreeIPA service. Incident Start time : 14:08 UTC August 13th, 2025

2. 13 août 2025 à 15:18 UTCresolved

   Our teams have successfully deployed a fix, and this incident is now resolved. Full service was restored as of 15:05 UTC. Between 14:08 UTC and 15:05 UTC, customers may have experienced issues accessing DataHubs, DataLakes, and FreeIPA services. Service should now be operating normally. If you are still experiencing any issues, please contact our support team. A full root cause analysis (RCA) will be published within seven business days.

3. 22 août 2025 à 18:15 UTCpostmortem

   A recent system update, intended to enhance stability of our platform, inadvertently led to an unforeseen memory issue affecting a critical internal service responsible for platform access management. ‌ A subsequent incoming request spike caused the memory limits exhaustion, which resulted in the service to become intermittently unavailable. ‌ The memory allocation for the service was manually increased, which restored normal operations. This change was then made permanent to circumvent any recurrence. ‌ We have implemented more robust monitoring and alerting to detect similar issues in the future before they can impact our customers. This includes updating the existing alerts for resource exhaustion and adding new alerts based on the incident, to ensure that the right teams are notified immediately. ‌ We are dedicated to providing a reliable and performant platform. We will continue to invest in improving our infrastructure and processes to prevent future disruptions. We appreciate your patience and understanding as we worked to resolve this issue.

1. 23 juin 2025 à 12:35 UTCidentified

   The daily consumption report that is available on the Cloudera Management Console has not been reporting current usage data since Thu Jun 19th 2025. Our teams have identified the source of the issue and are working on implementing a solution to make the data available by this Friday Jun 27th 2025, if not sooner. While the team is working on resolving the issue customers may use https://my.cloudera.com/account/usage to avail their consumption reports.

2. 24 juin 2025 à 07:08 UTCmonitoring

   Our teams have successfully deployed the fix. The data pipeline is running, and data up to 21st June is available. The backlog in consumption reporting data will be processed gradually. Meanwhile, customers may use https://my.cloudera.com/account/usage to get the consumption reports. Our teams are actively monitoring the situation.

3. 27 juin 2025 à 06:10 UTCresolved

   Our teams have confirmed that the issue has been resolved. The data pipelines have now caught up on the backlogged consumption reporting data. If you are still experiencing issues or have any questions, please raise a support case with us. A root cause analysis (RCA) will be published within seven business days.

4. 2 juillet 2025 à 06:14 UTCpostmortem

   On 23rd of June, we were notified that our Consumption Dashboards were not displaying current usage data from June 19th, 2024. Upon further investigation, we identified that the pipeline that ingests data into consumption was not progressing due to out-of-memory crash errors. The issue was caught and fixed, but the catch-up of the pipeline caused a delay of 2-3 days. While the reprocessing was happening in the background, customers could still use [https://my.cloudera.com/account/usage](https://my.cloudera.com/account/usage) to get the same consumption reports. Our teams have instituted preemptive measures and refined our internal protocols to manage similar incidents proactively in the future. We apologize for any inconvenience this may have caused and remain committed to implementing all necessary measures to prevent the recurrence of such issues.

1. 6 juin 2025 à 14:58 UTCresolved

   A temporary interruption in access to the DataCatalog service was detected by our internal monitoring systems. This interruption has been classified as transient, indicating that it was not a prolonged or persistent outage, though it did affect accessibility to the service for a brief period of time. Our technical teams are actively investigating the root cause of this disruption to understand precisely what occurred. An update will be disseminated as soon as the investigation concludes and a definitive explanation for the disruption is established.

2. 16 juin 2025 à 13:40 UTCpostmortem

   On June 3rd 2025 our internal systems detected intermittent 504 errors on the Data Catalog service UI. ‌ The interruption was caused by Data Catalog service components prematurely indicating they were ready to handle requests immediately after a scheduled system restart. In reality, these components were still performing essential internal data updates, a process which took approximately 24 minutes. During this period, the service was unable to fully process user requests, leading to intermittent access issues and 504 errors. ‌ To prevent similar occurrences, we have enhanced our system's readiness checks to ensure the Data Catalog service is fully prepared to serve traffic. ‌ We apologize for any inconvenience caused by the service disruption. We are committed to providing a reliable and robust platform and truly appreciate your understanding.

1. 3 avril 2025 à 11:41 UTCinvestigating

   Current Status: We are currently investigating a potential issue with US control plane service. We will have an update within 60 mins. Customer Experience: Login and CDP operations may be impacted.Running workload on clusters should not be impacted. Incident Start time: 6:30 UTC April 3rd, 2025

2. 3 avril 2025 à 12:42 UTCinvestigating

   Current Status: Our teams are continuing their investigation to determine the source of the issue. We will have another update within 60 mins. Customer Experience: Login and CDP operations may be impacted.Running workload on clusters should not be impacted. Incident Start time: 6:30 UTC April 3rd, 2025.

3. 3 avril 2025 à 13:47 UTCinvestigating

   Current Status: Our teams are continuing their investigation to determine the source of the issue. We have ruled out that its a Workload issue. We will have another update within 60 mins. Customer Experience: Login and CDP operations may be impacted. Incident Start time: 6:30 UTC April 3rd, 2025.

4. 3 avril 2025 à 15:25 UTCresolved

   Current Status: Our teams have successfully deployed a fix for the issue and confirmed that the issue has been resolved. If you are still experiencing issues or have any questions please raise a support case with us. A root cause analysis (RCA) will be published within seven business days. Customer Experience: Login and CDP operations via portal was impacted. API & CLI operations were working fine. Also workloads were not impacted. Incident Start time: 6:30 UTC April 3rd, 2025. Incident End time: 15:15 UTC April 3rd, 2025.

5. 15 avril 2025 à 19:49 UTCpostmortem

   On 3rd April 2025, there was an intermittent service disruption impacting login and CLI operations via the Management Console portal. Subsequent investigation identified the root cause stemmed from an increase in latency with internal DNS servers. In response, corrective measures were promptly taken to address the issue. Furthermore, we have implemented supplementary checks and preemptive actions to prevent similar occurrences in the future. We apologise for any inconvenience caused by the service disruption. We are fully committed to providing a reliable and robust platform and truly appreciate your understanding.

1. 12 mars 2025 à 18:02 UTCresolved

   Current Status: Our teams have identified the source of the intermittent issue impacting the FreeIPA service in the EU Control Plane. We have successfully deployed a fix for the issue and confirmed that the issue has been resolved. If you are still experiencing issues or have any questions please raise a support case with us. We sincerely apologize for any inconvenience this may have caused and we will have the root cause analysis (RCA) published within seven business days. Customer Experience: During this outage customers on the EU Control Plane may have experienced intermittent issues with the FreeIPA service, impacting its health status and autoscaling operations.

2. 9 avril 2025 à 13:50 UTCpostmortem

   On March 12, 2025, intermittent service disruptions were experienced due to an expired certificate served by an endpoint. Despite an automated successful certificate renewal, staggered pod restarts resulted in inconsistencies, with older ingress controller pods serving the expired certificate alongside a recently updated pod. This discrepancy led to intermittent user errors. Resolution was achieved through a systematic restart of all affected components, ensuring uniform application of the renewed certificate and restoring service consistency. We have also implemented measures to prevent similar occurrences. We sincerely apologize for any inconvenience this service disruption may have caused. We are committed to maintaining the highest standards of service reliability and appreciate your understanding.

1. 3 mars 2025 à 22:12 UTCidentified

   Current Status: Our teams have identified the source of the issue and have partially restored the services. We continue to work on a restoring the service and will have another update in the next 60mins. Customer Experience: During this window customers may experience issues logging into the console and potential slowness accessing the experiences. Incident Start time: 19:58 UTC March 3rd, 2025

2. 3 mars 2025 à 23:26 UTCidentified

   Current Status: Our teams are actively working on a permanent solution to fully restore the service. Please expect another update in 60 mins. Customer Experience: During this window customers may experience issues logging into the console and potential slowness accessing the experiences.

3. 4 mars 2025 à 00:27 UTCmonitoring

   Current Status: Our teams have successfully identified the source of the issue and have implemented a solution, which is currently under monitoring. Should you continue to experience issues logging into the console, we kindly request that you submit a support case to us for further assistance. We will keep you updated once we confirm that the issue is resolved on our end. Customer Experience: During this window customers may experience issues logging into the console and potential slowness accessing some services.

4. 4 mars 2025 à 00:40 UTCresolved

   Current Status: Our teams have successfully deployed a fix for the issue and confirmed that the issue has been resolved. If you are still experiencing issues or have any questions please raise a support case with us. A root cause analysis (RCA) will be published within seven business days. Customer Experience: During this window customers may experience issues logging into the console and potential slowness accessing some services.

5. 19 mars 2025 à 16:53 UTCpostmortem

   On March 03, 2025, a service disruption occurred within our EU Control plane. This disruption resulted from a configuration change implemented during a routine production cluster upgrade, which inadvertently triggered a synchronization error, leading to service unavailability. ‌ Upon detection of the issue, our engineering teams promptly allocated additional resources to the affected cluster. This action facilitated the restoration of services to an operational state. The root cause of the disruption was the result of an oversight during the standard upgrade procedure, which resulted in the synchronization failure. ‌ We sincerely apologize for any inconvenience this service disruption may have caused. We have implemented corrective measures and refined our upgrade protocols to mitigate the risk of similar incidents in the future. We are committed to maintaining the highest standards of service reliability and appreciate your understanding.

1. 30 janvier 2025 à 13:20 UTCidentified

   The daily consumption report that is available on the CDP Management Console has not been reporting current usage data since Thu Jan 23 2025 Our teams have identified the source of the issue and are working on implementing a solution to make the data available by this Friday Jan 31st 2025, if not sooner. While the team is working on resolving the issue; customers may use my.cloudera.com to avail their consumption reports.

2. 1 février 2025 à 10:46 UTCresolved

   Our teams have successfully deployed a fix for the issue and confirmed that the issue has been resolved. The data pipelines have now caught up on the backlogged consumption reporting data. If you are still experiencing issues or have any questions please raise a support case with us. Alternatively customers may use my.cloudera.com to get the consumption reports. A root cause analysis (RCA) will be published within seven business days.

3. 13 février 2025 à 15:38 UTCpostmortem

   On January 29, 2025, we were alerted to an issue affecting the display of usage data within our Consumption Dashboards. This issue, which began on January 23, 2025, was also flagged by our internal monitoring systems. Subsequent investigation identified a naming convention mismatch within a cluster, specifically an incompatibility with the designated string format. This discrepancy has been resolved by fixing the cluster’s name and enabling data to be reprocessed. While the reprocessing was happening in the background; customers were able to use [my.cloudera.com](http://my.cloudera.com) to get the same consumption reports. ‌To prevent similar occurrences, we have implemented proactive measures and refined our internal protocols for managing such incidents. We sincerely apologize for any inconvenience this disruption may have caused and are committed to preventing its recurrence.

1. 14 janvier 2025 à 20:46 UTCinvestigating

   Current Status: We are currently investigating a potential issue with CDP Management Console. We will have an update within 60 mins. Customer Experience: Customer may observe 404/Bad Gateways error while accessing CDP Management Console.

2. 14 janvier 2025 à 21:41 UTCresolved

   Current Status: Our teams have successfully deployed a fix for the issue and confirmed that the issue has been resolved. If you are still experiencing issues or have any questions please raise a support case with us. A root cause analysis (RCA) will be published within seven business days. Customer Experience: Customer may observe 404/Bad Gateways error while accessing CDP Management Console.

3. 27 janvier 2025 à 16:04 UTCpostmortem

   On January 13th, 2025, a few of our customers experienced service disruption with the Cloudera Management Console user interface, leading to customers encountering 404 and 5xx errors when navigating the console. This disruption stemmed from an unusually high volume of notification events. We have taken immediate action to handle this unexpected surge in events. We sincerely apologise for any inconvenience this may have caused and greatly appreciate your patience and understanding.

1. 13 janvier 2025 à 15:08 UTCresolved

   Current Status: Our teams have identified an issue effecting the authentication services while accessing workload URLs on the US Control Plane region. While a majority of the authentication request were working as expected, a small percentage of requests were impacted. The issue has been addressed and our teams are continuing to monitor it closely. If you are still experiencing issues or have any questions please raise a support case with us. A root cause analysis (RCA) will be published within seven business days. Customer Experience: During this outage customers may have experiences issues while accessing workload URLs on the US Control Plane region.

2. 23 janvier 2025 à 14:58 UTCpostmortem

   On Jan 9th,  Cloudera implemented a planned system change, affecting how customers accessed their CDP workloads URL's. This change inadvertently caused issues for customers who accessed their CDP workloads URL's before authenticating. Specifically, customers who had their identity provider \(IDP\) configured to expect a certain URL were experiencing authentication failures. This affected customers who initiated the authentication process from the service provider's side. Cloudera promptly rolled back the system change, restoring normal access to CDP workload URLs. We sincerely apologize for any inconvenience this disruption may have caused and appreciate your understanding and patience during this resolution.

1. 2 décembre 2024 à 19:29 UTCresolved

   Current Status: Our teams have identified an issue/degraded performance in the Control Plane US Prod Region. The issue has been addressed and our teams are continuing to monitor it closely. If you are still experiencing issues or have any questions please raise a support case with us. A root cause analysis (RCA) will be published within seven business days. Customer Experience: During this outage customers may have experiences issues with Control Plane operations. Incident Start time: 17:20 UTC December 2nd, 2024 Incident End time: 17:33 UTC December 2nd, 2024.

2. 13 décembre 2024 à 14:48 UTCpostmortem

   On December 2, 2024, between 17:20 - 17:33 UTC, our US Control Plane experienced a 13-minute service degradation. This incident occurred during routine maintenance of our internal infrastructure, where an error caused the unintentional degradation of nodes. We have taken immediate action to enhance our internal protocols and implement preventive measures to avoid similar incidents in the future. We apologise for any inconvenience caused and remain dedicated to ensuring a seamless experience for our valued customers. Thank you for your patience and understanding

1. 15 novembre 2024 à 12:41 UTCidentified

   Due to a recent disruption in Salesforce services, customers who use Cloudera Single Sign-On (CSSO) for accessing their Public Cloud Management console may experience login issues. Customers utilizing their own Identity Providers (IDPs) for Single Sign-On will not be affected by this service interruption. We appreciate your understanding and patience as we work through this matter. If you have any questions or need assistance, please do not hesitate to reach out to our support team at US: 1-866-809-4659 / International: 1-650-425-9421 Thank you for your continued support.

2. 15 novembre 2024 à 16:01 UTCresolved

   Our teams confirmed that our Cloudera Single Sign-on (CSSO) is now stable and operational. We apologize for any inconvenience this may have caused. If you are still experiencing issues or have any questions please raise a support case with us. Thank you for your continued support.

1. 22 octobre 2024 à 16:07 UTCinvestigating

   Current Status: The daily consumption report that is available on the CDP Management Console has not been reporting current usage data since Oct 16th. We are currently investigating a potential issue with the dashboard . Customer Experience: During this window customers may experience issues accessing daily consumption reports.

2. 22 octobre 2024 à 16:42 UTCidentified

   Current Status: The daily consumption report that is available on the CDP Management Console has not been reporting current usage data since Oct 16th. Our teams have identified the source of the issue and are working on implementing a solution to make the data available. The ETA will be approx. 4-5 days. While the team works on resolving the issue customers may use my.cloudera.com to get the consumption reports. Customer Experience: During this window customers may not be able to view data reported after 16th Oct.

3. 22 octobre 2024 à 18:02 UTCidentified

   We are continuing to work on a fix for this issue. While the team works on resolving the issue customers may use my.cloudera.com to get the consumption reports.

4. 24 octobre 2024 à 20:13 UTCresolved

   Our teams have successfully deployed a fix for the issue and confirmed that the issue has been resolved. The data pipelines are now up and running smoothly, and we have caught up on the backlogged consumption reporting data. If you are still experiencing issues or have any questions please raise a support case with us. Alternatively customers may use my.cloudera.com to get the consumption reports. A root cause analysis (RCA) will be published within seven business days.

5. 15 novembre 2024 à 14:06 UTCpostmortem

   On 22nd of October, we were notified about our Consumption Dashboards not displaying usage data after October 16th 2024. ‌ Upon further investigation, we identified that due to internal reprocessing of the consumption data our reporting dashboards were impacted. To address the issue our teams initiated workflows to reprocess the consumption data.  ‌ While the reprocessing was happening in the background; customers could still use [my.cloudera.com](http://my.cloudera.com) to get the same consumption reports. ‌ Our teams have instituted preemptive measures and refined our internal protocols to proactively manage similar incidents in the future. ‌ We apologize for any inconvenience this may have caused and remain committed to implementing all necessary measures to prevent the reoccurrence of such issues.

1. 18 septembre 2024 à 22:03 UTCidentified

   Our teams have identified an issue that impacts new installs and upgrades of the Cloudera Data Engineering (CDE) DataService on AWS. We are working a fix and we expect to know the ETA for the fix by the end of this week. We advise against planning any CDE environment upgrades till a fix is made available. Alternatively, you may seek assistance from our support team, who can provide guidance on implementing a manual workaround for the issue. Customer Experience: AWS Customers may observe issues while installing or upgrading Cloudera Data Engineering (CDE) DataServices. Further updates will be shared as we make progress on releasing the fix.

2. 20 septembre 2024 à 15:03 UTCidentified

   During the course of the investigation, we have been notified that customers deploying new Cloudera Data Engineering (CDE) services on Azure are also experiencing issues. This issue only affects new installations and upgrades of the CDE services; other operations are not impacted. We recommend that customers refrain from performing any upgrades until the fix is released, which is targeted for the end of this month. In the meantime, our support team is available to provide guidance on implementing a manual workaround for the issue. We regret any inconvenience caused by this situation and are working to have this resolved soon.

3. 30 septembre 2024 à 20:09 UTCresolved

   Current Status: We have successfully deployed a fix for the issue and confirmed that it has been resolved. Customers may now resume any pending upgrade activities on their Cloudera Data Engineering (CDE) services. We sincerely apologize for any inconvenience caused by this service disruption and are committed to providing a reliable and robust platform. We truly appreciate your understanding. If you are still experiencing issues or have any questions, please raise a support case with us.

1. 29 août 2024 à 18:09 UTCinvestigating

   Current Status: We are currently investigating a potential issue with FreeIPA service. We will have an update within 60 mins. Customer Experience: Customer may observe issues while performing control plane operations on environments.

2. 29 août 2024 à 18:53 UTCresolved

   Current Status: Our teams have successfully deployed a fix for the issue and confirmed that the issue has been resolved. If you are still experiencing issues or have any questions please raise a support case with us. A root cause analysis (RCA) will be published within seven business days. Customer Experience: During this window customers may have experienced issues with FreeIPA service showing unreachable. Incident Start time: 17:21 August 29th, 2024 UTC Incident End time: 18:11 August 29th, 2024 UTC

3. 12 septembre 2024 à 15:35 UTCpostmortem

   On August 29, 2024, our FreeIPA service experienced connectivity issues to our Control Plane service. Subsequent investigation identified the root cause stemmed from expiration of the CCMv2 certificate. In response, corrective measures were promptly taken to address the issue. Furthermore, we have implemented supplementary checks and preemptive actions to prevent similar occurrences in the future. We apologise for any inconvenience caused by the service disruption. We are fully committed to providing a reliable and robust platform and truly appreciate your understanding.

1. 16 juillet 2024 à 21:05 UTCresolved

   Current Status: Our teams have successfully deployed a fix for the issue and confirmed that the issue has been resolved. If you are still experiencing issues or have any questions please raise a support case with us. A root cause analysis (RCA) will be published within seven business days. Customer Experience: During this window customers who tried accessing their CDP Console using CSSO credentials were impacted

2. 23 juillet 2024 à 14:52 UTCpostmortem

   On 13th July 2024, Cloudera SSO logins to the CDP Public Cloud Console was affected due to the expiration of an internal certificate on our customer portal. The issue was rectified through the installation of new certificates. In response, we have instituted preemptive measures and refined our internal protocols to proactively manage similar incidents in the future. We apologise for any inconvenience this may have caused and remain committed to implementing all necessary measures to prevent the reoccurrence of such issues.