Changes / Dremio / Unable to start Azure-based project engines in Dremio Cloud
Dremio: Major incident: Unable to start Azure-based project engines in Dremio Cloud
Summary
A major incident prevented Azure-based project engines from starting in Dremio Cloud - Europe and Dremio Cloud - US, affecting customers’ ability to start engines. It started at 2024-02-27 00:58 UTC and was resolved at 2024-02-27 08:30 UTC, lasting 7 h 31 min. Dremio rolled out a fix to all environments and verified engines were starting.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Unable to start Azure-based project engines in Dremio Cloud
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2024-02-27 00:58 UTC
Before: not present
After: 2024-02-27 08:30 UTC
Before: not present
After: Dremio Cloud - Europe, Dremio Cloud - US
Before: not present
After: Users may be experiencing issues with starting engines in Dremio Cloud for Azure projects. We are currently investigating the issue. Expect updates every 30 minutes.
Before: not present
After: Users may be experiencing issues with starting engines in Dremio Cloud for Azure projects. We have identified the issue and are working on a fix. We will provide another update by 6:45 PM PT.
Before: not present
After: Users may be experiencing issues with starting engines in Dremio Cloud for Azure projects. We have identified the issue and are working on a fix. We will provide another update by 7:45 PM PT.
Before: not present
After: Users may be experiencing issues with starting engines in Dremio Cloud for Azure projects. We have identified the issue and are working on rolling out a fix. We will provide another update by 8:45 PM PT.
Before: not present
After: Users may be experiencing issues with starting engines in Dremio Cloud for Azure projects. We have identified the issue and are continuing to work on rolling out a fix. We will provide another update by 9:45 PM PT.
Before: not present
After: Users may be experiencing issues with starting engines in Dremio Cloud for Azure projects. We have identified the issue and are continuing to work on rolling out a fix. We will provide another update by 10:45 PM PT.
Before: not present
After: Users may be experiencing issues with starting engines in Dremio Cloud for Azure projects. We have verified a fix and are working on rolling out the fix to production environments. We will provide another update by 11:15 PM PT.
Before: not present
After: Users may be experiencing issues with starting engines in Dremio Cloud for Azure projects. We have verified a fix and are continuing to roll out the fix to production environments. We will provide another update by 11:45 PM PT.
Before: not present
After: Users may be experiencing issues with starting engines in Dremio Cloud for Azure projects. We have rolled out the fix to Dremio Cloud EU and are continuing to roll out the fix to Dremio Cloud US. We will provide another update by 12:15 AM PT.
Before: not present
After: Users may be experiencing issues with starting engines in Dremio Cloud for Azure projects. We have rolled out the fix to Dremio Cloud EU and are completing the roll out of the fix to Dremio Cloud US. We will provide another update by 12:45 AM PT.
Before: not present
After: We have rolled out the fix to all Dremio Cloud environments and have verified engines are coming up for Azure-based projects. We apologize for any inconvenience this incident may have caused.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Unable to start Azure-based project engines in Dremio Cloud (this change) A major incident prevented Azure-based project engines from starting in Dremio Cloud - Europe and Dremio Cloud - US, affecting customers’ ability to start engines. It started at 2024-02-27 00:58 UTC and was resolved at 2024-02-27 08:30 UTC, lasting 7 h 31 min. Dremio rolled out a fix to all environments and verified engines were starting. | Major incident |