Hello Larry Skeen,
It looks like you're experiencing an issue with duplicate entries for your Linux server in Azure Arc after onboarding it multiple times. Here’s a step-by-step approach you can try to clean up the stale entry:
- Verify Machines in Azure Portal: Go to the Azure Portal and navigate to the Azure Arc section. Check if you can identify both entries for the server (rf-ms-chkpntlog): one in the correct resource group and the other in the deleted resource group.
- Force Refresh: Sometimes, the sync might take a bit longer. To refresh the state, you can try running the following command in Azure CLI to see if this helps:
- az connectedmachine show --resource-group RefuelSEIM --name rf-ms-chkpntlog
- Use Azure CLI to Delete the Stale Entry: Since you mentioned you've tried using the CLI without success, ensure you're using the correct command format. You can run:
- az connectedmachine delete --resource-group rf-monitor-syslog --name rf-ms-chkpntlog
Note: Ensure the resource group name in the command matches exactly where the stale entry is shown.
- Check for Dependencies: If the stale entry fails to delete, check if there are any dependencies or locks applied on that resource that might prevent deletion.
- Contact Microsoft Support: If none of these steps work, it might be best to reach out to Azure Support directly for further assistance. They can help resolve issues related to orphaned entries in the Azure Arc service.
Hope this helps you clean up the duplicate entry! If you need any more assistance or if these steps don’t resolve the issue, feel free to ask.
Relevant Documentation Links:
- Troubleshoot Azure Arc-enabled servers agent connection issues
- Connect hybrid machines to Azure from the Azure portal
- Azure Arc for Servers Overview
Let me know if you need more information!