I am encountering an error while running pipelines on Azure DevOps and unable to resolve it. As an agent ready for the job connecting.., I require your assistance in resolving this issue. Please let me know what information you need to assistance.

Question

I am encountering an error while running pipelines on Azure DevOps and unable to resolve it. As an agent ready for the job connecting.., I require your assistance in resolving this issue. Please let me know what information you need to assist. I am available for clarification.

Answer 1

Hi Rameez Sheraz,

Please note that Azure DevOps related questions are not supported on this forum. It's better to reach out to dedicated forum here.

However, by visiting https://status.azure.com/en-us/status, you can see the full status of the outage. Quoting below:

Impact Statement: Starting around 20:19 UTC on 7 February 2023, a utility power surge in the Southeast Asia region tripped a subset of the cooling units offline in one of the Availability zones. While working to restore the cooling units, temperatures in the datacenter increased so we have proactively powered down a small subset of selected compute and storage scale units, to avoid damage to hardware and reduce cooling system load. All impacted storage and compute scale units are in the same datacenter, within one of the region’s three Availability Zones (AZs). Multiple downstream services have been identified as impacted. Current Status: We do not have an exact ETA at this time, we currently expect an extended period of time to fully restore all cooling capacity. The Azure service recovery process will commence at this time and is expected to progressively return over a number of hours. Due to the nature of this issue our storage scale units are expected to require significant recovery efforts to ensure all resources return in a consistent state. Note that any new allocations for resources will automatically avoid the impacted scale units. If your workloads are protected by Azure Site Recovery or Azure Backup, we recommend to either initiate a failover to the recovery region or recover using Cross Region Restore. Customers using services that are zonally-aware may consider failing out of the impacted zone, physical zone AZ-03. Note that physical zones are mapped to logical zones in your Azure subscription, Refer to: https://learn.microsoft.com/rest/api/resources/subscriptions/check-zone-peers. This message was last updated at 07:40 UTC on 08 February 2023