Share via

Arc servers machines are already connected to a different subscription id or resource group when creating cluster in Azure portal

Wang, Bill (Solution Software Engineering) 20 Reputation points
2024-10-24T00:50:11.9366667+00:00

I am using azure portal to create a cluster but ran into an issue during Azure Stack HCI Arc Integration validation.

"Title": "Test Arc for servers machines state", "Status": 1, "Severity": 2, "Description": "Check if Arc for servers machines are already connected to a different subscription id or resource group", "Remediation": "https://learn.microsoft.com/en-us/azure-stack/hci/deploy/deployment-tool-prerequisites", "TargetResourceID": "7c70d5cc-090b-45ce-81a3-b2b798d39bf0/SBE_E920_03/E920N1,E920N2", "TargetResourceName": "E920N1,E920N2", "TargetResourceType": "Arc for Servers", "Timestamp": "/Date(1729722723214)/", "AdditionalData": { "Detail": "Following cluster node(s) are already Arc enabled with a different ARM Resource Id: 192.168.1.100: Subscription Id: 7c70d5cc-090b-45ce-81a3-b2b798d39bf0, Resource Group: SBE_E920_7 are the current parameters to which the arc agent is connected. 

I used to have SBE_E920_03 in my resource group, and my colleague once created a cluster with the same node in his resource group, SBE_E920_03, but both resource groups SBE_E920_03 were removed.

Now I try to use the same nodes to create a cluster, but it keeps showing this error.

How can I fix this issue?

Azure Cloud Services
Azure Cloud Services
An Azure platform as a service offer that is used to deploy web and cloud applications.
704 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
1,014 questions
0 comments
Accepted answer
  1. Sai Krishna Katakam 1,085 Reputation points Microsoft Vendor
    2024-10-24T06:58:26.1233333+00:00

    Hi Wang, Bill (Solution Software Engineering),

    Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

    The issue you're encountering occurs because the Azure Arc-enabled servers are still connected to a different subscription or resource group, even though those resources may have been deleted. To resolve this, you need to unregister the Azure Arc-enabled nodes from their previous configuration before reusing them to create a new cluster.

    Unregister the existing Azure Arc configuration:

    • Open Azure Portal.
    • Go to Azure Arc > Servers.
    • Locate the Arc-enabled servers associated with the previous resource group (e.g., SBE_E920_03).
    • Select each server and choose Delete or Unregister. This will remove the current Arc configuration from Azure.

    Re-register the servers with the correct subscription and resource group:

    • After unregistering, re-enable Azure Arc on the servers by running the Azure Arc onboarding script again, making sure to connect to the correct subscription and resource group.

    After completing these steps, rerun the Azure Stack HCI Arc Integration validation to ensure everything is correctly configured.

    For more information, please refer to below documents:
    Azure Stack HCI Arc deployment prerequisites.
    Azure Arc-enabled servers
    Troubleshoot Azure Connected Machine agent connection issues

    If you have any further queries, do let us know. If the comment is helpful, please click "Upvote".

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.