AS HCI ARM Deployment Fail : No updates received from device for operation

Question

OperationTimeout , No updates received from device for operation: [providers/microsoft.azurestackhci/locations/WESTEUROPE/operationStatuses/d2596df1-9b80-44a5-bf09-45fedc8f573e*26482831E1D30488101337537ACFA672FEE5984DFEDD96846A94A1A83DFF3073?api-version=2024-04-01] beyond timeout of [600000] ms
 (Code: ArcOperationTimedOut, Target: /subscriptions/6c1385f1-c814-43c7-8b24-dbeb838d815c/resourceGroups/RG-HCI/providers/Microsoft.HybridCompute/machines/HCI-NODE1)

My Deployment keeps failling with this error message
I have tried everything I can think off, also reinstalled my nodes completelly, no help.
Does somebody have a solution to this?

Answer 1

Well the exact same thing Copilot told me, so it doesn't help for sure. I wouldn't come here to ask before I double check everything...

The problem is in Azure itself and they tell you this only when you contact them directly, and problem is not published in Well-Known Issues who knows why. (they also tell you that) They say that problem is with LCM Extension Update and it will/should be solved with next update. Workaround is to delete everything in Resource Group except for Nodes (and storage account if needed for witness), to set UTC time zone on every node and reboot them. Then after rebooting to make sure that LcmController Service is running, which mostly won't be the case so you start it manually and then redeploy ARM Template. It should work and later you can get your timezone back.

Answer 2

Hi Radovan Sukic,
Welcome to the Microsoft Q&A Platform and thank you for posting your query here. Based on your query, I understand your concern. The issue you are facing could be due to several factors, and we cannot confirm the exact cause at this time.
Could you please try this thing ensure stable network connectivity between your nodes and Azure services, as interruptions can cause timeouts. Verify that required Azure resources are available and there are no service outages in your region. Check your configuration settings carefully, including network setups, resource groups, and permissions, as misconfigurations can lead to failures. If operations are timing out, consider extending the timeout value. Lastly, ensure your nodes have sufficient resources, such as CPU and memory, to handle the workload and meet Azure Stack HCI requirements

Please let us know if you have any concerns regarding this issue, or if you need any additional information, don’t hesitate to reach out. We are always here to support you and address your concerns with the highest level of care and attention.