moc-operator virtualmachine serviceClient returned an error while reconciling

Question

Hi Team,

I am facing the below error when i am trying to create a Vm in Azure Stack HCI.

My Cluster have 4 Node with OS 23H2 and build as 25398.2092.

{

"code": "Unknown",

"message": "moc-operator virtualmachine serviceClient returned an error while reconciling: rpc error: code = Unknown desc = Exception occurred. (Generic failure )",

"additionalInfo": [

{

  "type": "ErrorInfo",

  "info": {

    "category": "Uncategorized",

    "recommendedAction": "",

    "troubleshootingURL": ""

  }

}

]

}

Answer 1

Hello @rajneesh kumar

Yes, your research is on-point.

The VM creation failure from the moc-operator is expected with the cluster being in ConnectionStatus: OutOfPolicy.

According to Microsoft, if an Azure Local (formerly called Azure Stack HCI) cluster has not successfully connected and synced with Azure for more than 30 days, the platform intentionally enters a reduced‑functionality mode. In this state, existing VMs continue to run, but creation of new VMs is blocked until the cluster returns to a healthy, connected state.

The positive takeaway is that this behavior is expected and by design. You are also already taking the correct approach by engaging Microsoft support and the product teams to help clear the OutOfPolicy condition and bring the cluster back to a connected state.

Once Microsoft confirms that the cluster has successfully re-synchronized with Azure, VM creation should work as expected.

Answer 2

The error message you are encountering indicates a generic failure during the reconciliation process of the virtual machine creation in Azure Stack HCI. This type of error can occur due to various reasons, including issues with the cluster configuration, resource availability, or underlying infrastructure problems.

Here are some steps you can take to troubleshoot this issue:

1. Check Cluster Health: Ensure that all nodes in your cluster are healthy and that there are no underlying issues affecting the cluster's operation.
2. Review Logs: Examine the MOC guest agent logs for more detailed error messages that might provide insight into the failure. The logs can be found in the following locations:
   • For Windows VMs: C:\ProgramData\mocguestagent\log\
   • For Linux VMs: sudo journalctl -u for critical logs and /opt/mocguestagent/log/ for operational logs.
3. Resource Availability: Verify that there are sufficient resources (CPU, memory, storage) available in the cluster to create the VM.
4. Permissions: Ensure that you have the necessary permissions to create VMs in the Azure Stack HCI environment.
5. Retry: Sometimes, transient errors can occur. Attempt to create the VM again after a short wait.

If the issue persists after following these steps, consider reaching out to Microsoft Support for further assistance.

---

References:

• Troubleshoot Azure Local Virtual Machines enabled by Azure Arc
• Collect log files for Azure Local VMs enabled by Azure Arc
• Known issues: VMs on Azure Stack Hub
• Understand common error messages when you manage virtual machines in Azure