update ARB and extenstions errors

Question

update ARB and extenstions errors

Joe Comeau 40

While doing an update on our azure local, we encountered an issue:

Logs: (error details):

Type 'UpdateArbAndExtensions' of Role 'MocArb' raised an exception: [Update-k8sExtensionInternal] Update-k8sExtensionInternal failed to reach succeeded status - [] Command Arguments ------- --------- Update-k8sExtensionInternal {clusterName=hci01-arcbridge, releaseTrain=stable, resourceGroupName=hci01-rg, extens... UpgradeArbAndExtensionsInternal {Parameters=CloudEngine.Configurations.EceInterfaceParameters} {} <ScriptBlock>

[REDACTED]

Ankit Yadav 14,165 Reputation points Microsoft External Staff Moderator

2026-02-23T05:35:04.1133333+00:00

Here's an update for the thread: The issue has been escalated internally at Microsoft to the Engineering team for further investigation and troubleshooting. We will provide more information here as soon as we have it.

Thank you for your patience as we work on resolving this.
Jilakara Hemalatha 12,915 Reputation points Microsoft External Staff Moderator

2026-02-24T08:42:32.4466667+00:00

Hello Joe,

As discussed with the Product Group, the environment is currently on the 2411 build. Recreating the Azure Resource Bridge (ARB) on this build may introduce certain side effects and known issues for Arc-managed resources.

If there are no Arc-managed resources in the environment, we can proceed with the ARB recreation directly. However, if Arc-managed resources are present, we need the below details to plan the recovery safely:

Are there any Hybrid AKS resources on the cluster?

Were any of the VMs created using an image that no longer exists in Azure?

Are there any VMs that cannot tolerate a temporary network disconnection during the activity?

Are any of the VMs Windows machines configured with static IP addresses?

This information will help us assess the impact and determine the appropriate next steps.

Answer accepted by question author

0 additional answers

Your answer

Ankit Yadav 14,165 Reputation points Microsoft External Staff Moderator

2026-02-23T05:35:04.1133333+00:00

Here's an update for the thread: The issue has been escalated internally at Microsoft to the Engineering team for further investigation and troubleshooting. We will provide more information here as soon as we have it.

Thank you for your patience as we work on resolving this.
Jilakara Hemalatha 12,915 Reputation points Microsoft External Staff Moderator

2026-02-24T08:42:32.4466667+00:00

Hello Joe,

As discussed with the Product Group, the environment is currently on the 2411 build. Recreating the Azure Resource Bridge (ARB) on this build may introduce certain side effects and known issues for Arc-managed resources.

If there are no Arc-managed resources in the environment, we can proceed with the ARB recreation directly. However, if Arc-managed resources are present, we need the below details to plan the recovery safely:

Are there any Hybrid AKS resources on the cluster?

Were any of the VMs created using an image that no longer exists in Azure?

Are there any VMs that cannot tolerate a temporary network disconnection during the activity?

Are any of the VMs Windows machines configured with static IP addresses?

This information will help us assess the impact and determine the appropriate next steps.

Answer 1

Jilakara Hemalatha 12,915 Microsoft External Staff Moderator

Hello Joe Comeau,

The issue initially occurred during the ARB and extension update due to a misconfigured Arc Gateway setup, where the environment was placed in an unsupported state by enabling Arc Gateway after deployment on Azure Stack HCI version 2411. This resulted in proxy inconsistencies, with traffic being routed through localhost:40343 without proper backend configuration, causing connectivity failures and blocking the update process.

Following the guidance from the engineering team, the Arc Gateway association was removed from the affected node, which restored the system to a supported direct connectivity model. After validating that the proxy and gateway settings were cleared, the solution update was retried using PowerShell. The update for version 10.2411.2.12 proceeded successfully, and the environment was then upgraded further to version 10.2411.3.2.

During the subsequent update, the process appeared to be stuck for an extended duration. This behavior was identified as a known issue in certain builds where back-to-back updates can cause delays or failures, particularly during secret rotation or due to ECE agent slowness. Although initial troubleshooting steps, including following the recommended TSG for update slowness, were attempted, the update remained in a prolonged in-progress state.

Since this is not directly related to the original Arc Gateway misconfiguration issue, we recommend create a new Q/A post for this behavior so that it can be investigated further with the engineering team.

Vaughn DeFouw 81

I have tried to post a new post, and it won't let me. I have a similar error where my upgrade fails on the ARB and extensions but is says it's due to a client secret.

I'm trying to upgrade to 2025.04 Feature Update v21 of Azure Local. I located the App ID in the backend and updated the credential, but it refuses to proceed. I have tried a few methods to update the credential on the cluster - but apparently nothing has worked.

What is the procedure on Solution version 10.2503.0.13 to properly update the credential?

Here is the specific error:

Update task update ARB and extensions Result Error Start time 4/23/2026, 9:57 PM End time 4/27/2026, 12:52 PM Description update ARB VM and vm extensions inside of ARB VM Error details Type 'UpdateArbAndExtensions' of Role 'MocArb' raised an exception: [[UpgradeArbAndExtensions] Login to Az Cli Session using SPN] Logging into Azure CLI using SP failed after [5] retries. Error =  ERROR: AADSTS7000215     :Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret     added to app '[APPID]'. Trace ID: ca696aca-c38b-45cb-8cd6-9457c0146d00 Correlation ID:     94e57bf2-f396-47fb-a0b9-6248333f077f Timestamp: 2026-04-27 17:51:59Z at  at Login-AzCliSessionWithSPN, C:\NugetStore\Microsoft.AzureStack.MocArb.LifeCycle.1.2504.0.7\content\Scripts\MocArbHelper.psm1: line 3612 at Login-AzureForMocarb, C:\NugetStore\Microsoft.AzureStack.MocArb.LifeCycle.1.2504.0.7\content\Scripts\MocArbHelper.psm1: line 4170 at UpgradeArbAndExtensionsInternal, C:\NugetStore\Microsoft.AzureStack.MocArb.LifeCycle.1.2504.0.7\content\Scripts\MocArbHelper.psm1: line 2590 at UpdateArbAndExtensions, C:\NugetStore\Microsoft.AzureStack.MocArb.LifeCycle.1.2504.0.7\content\Scripts\MocArbLifeCycleManager.psm1: line 425 at <ScriptBlock>, C:\Agents\Microsoft.AzureStack.Solution.ECEWinService.10.2504.0.932\content\ECEWinService\InvokeInterfaceInternal.psm1: line 147 at Invoke-EceInterfaceInternal,

Share via

update ARB and extenstions errors

0 additional answers

Your answer