Troubleshoot accepted cluster resources

Azure Operator Nexus relies on mirroring, or hydrating, resources from the on-premises cluster to Azure. When this process is interrupted, the cluster resource can move to the Accepted state.

Diagnosis

The cluster status is viewed via the Azure portal or the Azure CLI.

az networkcloud cluster show --resource-group <RESOURCE_GROUP> --name <CLUSTER_NAME>

Mitigation steps

Follow these steps for mitigation.

Trigger the resource sync

1. From the cluster resource page in the Azure portal, add a tag to the cluster resource.

2. The resource moves out of the Accepted state.

   az login
   az account set --subscription <SUBSCRIPTION>
   az resource tag --tags exampleTag=exampleValue --name <CLUSTER> --resource-group <CLUSTER_RG> --resource-type "Microsoft.ContainerService/managedClusters"
   

Verification

After the tag is applied, the cluster moves to the Running state.

az networkcloud cluster show --resource-group <RESOURCE_GROUP> --name <CLUSTER_NAME>

If the cluster resource maintains the state for more than five minutes, contact Microsoft support.

Related content

• For more information about how resources are hydrated, see Azure Arc-enabled Kubernetes.
• If you still have questions, contact Azure support.
• For more information about support plans, see Azure support plans.