Failed to onboard azure stack hci node - with GUI and Powershell

Question

Hi everyone i have been trying since yesterday to do hci node onboard with azure arc. i followed the procedures given in the doc

https://learn.microsoft.com/en-us/azure-stack/hci/deploy/deployment-arc-register-server-permissions?tabs=powershell#assign-required-permissions-for-deployment

Both with the graphical way and with the powershell procedure with exactly the commands given in the guide

If i try from powershell i get stuck in a loop

Waiting for bootstrap to complete, Status: InProgress

NetworkConfig : NotApplicable

RemoteConfig : NotApplicable

WebProxy : NotApplicable

TimeServer : NotApplicable

HostName : NotApplicable

ArcConfiguration : NotStarted

ArtifactsUpload : NotStarted

ArcRegistration : NotStarted

ArcExtensionInstall : NotStarted

Update : NotStarted

with error AZCM0026

If I use the Web part instead I get the same error.

I would like to point out that machine hostname is resolvable by internal dns and port 443 is open for the node (inbound and outbound)

AzStackHciEnvironmentChecker.log

AzStackHciArcIntegration.log

Answer 1

Hi Samuele Provvedi,

Thank you for reaching to us back again with further information.

In PowerShell, it is correct to keep a space between the parameter and its value, and you can also put the value in quotes.
This should work for you.
Subscription = "yy49daaa-8115-abcd-99d8-3c0fe8939aXX"

$RG = "azshciprod-002"

$Region = "West Europe" (If a parameter value contains spaces, it must be enclosed in quotes).

$Tenant = "yy4cc6ua-e962-44f2-abcd-c4fab714f0XX"

As you mentioned, it indicates an error in network configuration, or some critical services are temporarily unavailable. Have you done the troubleshooting step mentioned in the document?
If the network is configured for Private Link Scope, a Private Link Scope resource ID must be provided for onboarding using the --private-link-scope parameter.

Then your command should look like below:

Invoke-AzStackHciArcInitialization -SubscriptionID $Subscription -ResourceGroup $RG -TenantID $Tenant -Region $Region -Cloud "AzureCloud" -ArmAccessToken $ARMtoken -AccountID $id -Proxy $ProxyServer --private-link-scope <Private_Link_Scope_Resource_ID>

I suggest you try the workaround and please do let us know if you have any further queries!

Thank You!

Answer 2

Hi!

@Samuele Provvedi -Yes, the region has to be entered without spaces:

$Region = "WestEurope" 

I had the very same issue and got the misleading error code "AZCM0026" until I specified the region as "WestEurope" and not "West Europe".

Here are the exact commands I used:

#Define the subscription where you want to register your server as Arc device
$Subscription = "0005dd00-d006-0a10-8000-000071300000"
#Define the resource group where you want to register your server as Arc device
$RG = "rg-weu-azshci"
#Define the region you will use to register your server as Arc device
$Region = "WestEurope"
#Define the tenant you will use to register your server as Arc device
$Tenant = "003b0000-9600-4300-9004-aa0024d00000"

Invoke-AzStackHciArcInitialization -SubscriptionID $Subscription -ResourceGroup $RG -TenantID $Tenant -Region $Region -Cloud "AzureCloud" -ArmAccessToken $ARMtoken -AccountID $id

AzureStack 23H2 with AzSHCI.ARCInstaller 1.2408.0.3053

Hope this helps!