Azure Stack HCI - Arc - Custom location is not shown

Question

Azure Stack HCI - Arc - Custom location is not shown

Divyesh Govardhanan 0

While creating Azure Stack HCI Cluster 23H2 from Azure portal, Custom location is not mapped to the cluster, when tried to create it manually from the Azure portal it shows only the Kubernetes clusters. User's image

Trent Helms - MSFT 2,541 Reputation points Microsoft Employee

2024-01-30T15:39:58.1666667+00:00

Hi,

The creation and mapping of the custom location should happen during the deployment process itself. You can't use existing custom locations. Can you confirm if you were using the portal or template deployment method and that you specified the name of the custom location you wanted to be created at the time of the deployment?

Hope this helps!
Divyesh Govardhanan 0 Reputation points

2024-01-31T06:53:50.65+00:00

Initially, I attempted to create the cluster using the portal, but it encountered a validation error as given in the image below, Whereas the extensions are already enabled. Consequently, I opted for a manual deployment on the HCI machine and successfully registered the cluster.

I would greatly appreciate your input if you have any insights or recommendations regarding the portal deployment issue.
Trent Helms - MSFT 2,541 Reputation points Microsoft Employee

2024-01-31T13:44:48.4366667+00:00
Hi,

For 23H2, there are only two types of deployments that are supported at this time. One is the portal experience which you are noting above. The second is via an ARM template. This method is useful when you plan to do lots of deployments. Note that you can save your template when completing a deployment from the portal, modify it and use it for subsequent ARM template deployments.

Manual deployments where you perform all of the actions of joining the nodes to the domain, creating the cluster and registering to Azure are not supported in 23H2. These clusters must be deployed via one of the two methods mentioned above where these actions are performed as part of the deployment with the proper extensions.

Given the error you are seeing, it would seem that either the hosts were not cleaned up properly after a previously failed deployment attempt or the extensions were installed incorrectly. Since you have done a manual deployment, the only way to fix this would be starting over. I would recommend starting with this document and ensuring all of the prerequisites are in place. Then follow each step carefully, and the guide will walk you through a deployment. Do not skip any steps and be sure to read each step carefully. You will need to reload the nodes as well as delete any resources from Azure that you created for the initial and/or manual deployment attempts. It is step 4. Register with Arc and set up permissions where the extensions are installed to the nodes which should take care of the error you received above.

If you run into issues before the deployment starts, you can reset your configuration and start over using the steps below. Note that if the deployment itself fails, these steps won't work and you will need to start over completely.

From the Azure portal, delete everything from the resource group EXCEPT the nodes.

Click on each node, go to Extensions and confirm the three required extensions are installed and healthy.

AzureEdgeDeviceManagement

AzureEdgeLifecycleManager

TelemetryAndDiagnostics

Reboot the nodes and ensure the LCMController service is running.

Get-Service LCMController

Return to the 'Deploy' option in the Azure portal and try again.

Hope this helps!
Mubarish Ahmed A 25 Reputation points

2024-02-02T07:16:06.1233333+00:00

Hi Trent, While creating the cluster from azure, in the validation steps I'm getting this below error message from the Environment checker validation. Can you please guide us on this? Is this related to Active directory credentials?
Trent Helms - MSFT 2,541 Reputation points Microsoft Employee

2024-02-05T13:34:13.49+00:00

Hi @Mubarish Ahmed A ,

Please post your question into a new thread. We are here to help, but posting into a new thread allows us to better understand the ask and allows others to benefit when reviewing answers.

Thanks so much!

Your answer

Trent Helms - MSFT 2,541 Reputation points Microsoft Employee

2024-01-30T15:39:58.1666667+00:00

Hi,

The creation and mapping of the custom location should happen during the deployment process itself. You can't use existing custom locations. Can you confirm if you were using the portal or template deployment method and that you specified the name of the custom location you wanted to be created at the time of the deployment?

Hope this helps!
Divyesh Govardhanan 0 Reputation points

2024-01-31T06:53:50.65+00:00

Initially, I attempted to create the cluster using the portal, but it encountered a validation error as given in the image below, Whereas the extensions are already enabled. Consequently, I opted for a manual deployment on the HCI machine and successfully registered the cluster.

I would greatly appreciate your input if you have any insights or recommendations regarding the portal deployment issue.
Mubarish Ahmed A 25 Reputation points

2024-02-02T07:16:06.1233333+00:00

Hi Trent, While creating the cluster from azure, in the validation steps I'm getting this below error message from the Environment checker validation. Can you please guide us on this? Is this related to Active directory credentials?
Trent Helms - MSFT 2,541 Reputation points Microsoft Employee

2024-02-05T13:34:13.49+00:00

Hi @Mubarish Ahmed A ,

Please post your question into a new thread. We are here to help, but posting into a new thread allows us to better understand the ask and allows others to benefit when reviewing answers.

Thanks so much!

Share via

Azure Stack HCI - Arc - Custom location is not shown

Your answer