Azure West US 2 Unhealthy Node Issue
Incident Report for Workspot
Resolved
We believe the issue with the unhealthy node in Azure WEST US 2 to be resolved at this point.
If you have VM Desktops in the Azure WEST US 2 region and end users are experiencing issues with them, please open a Workspot Support Ticket through the Control Support Portal.
Thank you.
Posted Oct 06, 2021 - 20:50 UTC
Monitoring
Azure has notified us of a hardware issue in the West Us 2 region that may be impacting you. 

Starting at 20:54 UTC on 05 Oct 2021, you have been identified as a customer using Virtual Machines in West US 2 who may experience connection failures and increased network latency when attempting to access some Virtual Machines hosted in the region.

Our monitoring has identified packet corruption between a network switch and server where your Virtual Machine(s) are deployed. We are removing the server in a degraded state from production to prevent additional deployments and further impact.

Your Virtual Machine(s) remain operational, but potentially in a degraded state on the faulty hardware for 24 hours after this notification. Customers that stop then start their Virtual Machine within 24 hours of this notification will restart on healthy hardware. Virtual machines remaining on the node after 24 hours will be live migrated to a healthy node.


What this means for you is that if your end users are experiencing a lot of latency in their connection or they are being disconnected/unable to connect to their VM Desktop as usual, then please use the redeploy action in the pools page in Control. This will move the VM Desktop to a new 'healthy' host/node. 

End users who are on the identified unhealthy host may not experience the issues described. Azure will automatically move those desktops to a healthy host at approximately 20:00 UTV (1pm PT) today, Wednesday 06OCT21. And exact time cannot be provided. 


If you have any questions, please feel free to reach out to your Customer Success Team member.


Thanks,
Workspot Support
Posted Oct 06, 2021 - 19:10 UTC
This incident affected: Workspot Control.