[Bug] Azure Local 2610 deployment fails during Arc/Network configuration due to backend API registration mismatch
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 35/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- azure, powershell
- 領域
- cloud, infrastructure
研究方向
Start by tracing the reported DeployArb / Install-ArcHciMgmt path in ArcHci.psm1, especially Install-ArcHciHybridAKSExtension near line 4965, and check the deployment package's networkProfiles API version. Compare those values with the Azure Arc extension catalog and Microsoft.AzureStackHCI provider metadata for the affected region. Done means a deployment using the reported solution version completes the Arc infrastructure phase without either registration error.
由索引模型根據 Issue 內容生成。
描述
[Bug] Azure Local 2610 Deployment Failure: API Version & Registration Mismatch in Backend (Microsoft.HybridAKSOperator & clusters/networkProfiles)
Title
[Bug] Azure Local 2610 deployment fails during Arc/Network configuration due to backend API registration mismatch
Description
Overview
During a clean deployment of Azure Local (Azure Stack HCI) 2610 using Solution Version 12.2610.1004.50, the orchestration consistently fails during the "Deploy Arc infrastructure components" phase.
The failure stems from a backend API registration and catalog synchronization issue:
- The local deployment scripts execute hardcoded CLI calls requesting the Kubernetes extension
Microsoft.HybridAKSOperatorversion7.2.12on thestablerelease train, which is rejected by the Azure API. - The deployment path for network profiles targets API version
2026-03-15-previewfor child resource typeMicrosoft.AzureStackHCI/clusters/networkProfiles/default. However, the Azure Resource Provider backend currently registers and accepts only2026-11-01-previewacross regions, producing persistentNoRegisteredProviderFounderrors.
Core cluster creation and deployment prerequisites succeed prior to this step, confirming that the issue is isolated to resource provider API compatibility and extension version registration in the Azure control plane.
Detailed Technical Analysis
1. Arc Extension Failure (Microsoft.HybridAKSOperator)
During the DeployArb role execution (Install-ArcHciMgmt), the orchestration engine runs the following command via Azure CLI:
az.cmd k8s-extension create \
--cluster-type appliances \
--cluster-name "contoso-cl-arcbridge" \
--resource-group "rg-contoso-azure-local-gwc" \
--name "hybridaksextension" \
--extension-type Microsoft.HybridAKSOperator \
--release-train stable \
--version 7.2.12 \
--auto-upgrade False \
--config-file C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\MocArb\WorkingDirectory\Appliance\aks-extension-config.json \
--only-show-errors
This returns an ExtensionOperationFailed exception:
ERROR: (ExtensionOperationFailed) The extension operation failed with the following error:
Failed to resolve the extension version from the given values.
InnerError: 'Extension type 'microsoft.hybridaksoperator' does not support release train 'stable' for version '7.2.12'.
Please try again with release train "stable".
The error message contains a contradictory directive ("does not support release train 'stable' ... Please try again with release train 'stable'"), indicating that version 7.2.12 is not properly mapped to the stable release train in the global Azure Arc catalog for the target region.
2. Resource Provider API Mismatch (clusters/networkProfiles)
Correlating support portal activity logs and deployment telemetry reveals a corresponding mismatch on the cluster network profile child resource (Microsoft.AzureStackHCI/clusters/networkProfiles/default):
- The local deployment package requests API version:
2026-03-15-preview. - Querying the
Microsoft.AzureStackHCIprovider capabilities forclusters/networkProfilesconfirms that only2026-11-01-previewis currently registered:
{
"resourceType": "clusters/networkProfiles",
"locations": [
"South Central US",
"East US",
"UK South",
"UK West",
"Germany West Central",
"Australia East",
"West Europe",
"Southeast Asia",
"Canada Central",
"Japan East",
"Central India"
],
"apiVersions": [
"2026-11-01-preview"
],
"capabilities": "None"
}
Because legacy versions (such as 2026-03-15-preview) are unlisted across all supported regions, calls targeting that version fail with NoRegisteredProviderFound.
Steps to Reproduce
- Prepare a host system with Azure Local (Azure Stack HCI OS) build 2610.
- Launch a new deployment targeting Solution Version
12.2610.1004.50ingermanywestcentral(or any region where only2026-11-01-previewis registered). - Complete initial hardware and infrastructure validation checks.
- Execute deployment until the "Deploy Arc infrastructure components" phase.
- The task fails at
DeployArb/Install-ArcHciMgmt.
Observed Error Stack Trace (Anonymized)
Type 'DeployArb' of Role 'MocArb' raised an exception: [DeployArb:Calling Install-ArcHciMgmt]
Correlation ID: 00000000-0000-0000-0000-000000000000
az.cmd k8s-extension create --cluster-type appliances --cluster-name "contoso-cl-arcbridge" \
--resource-group "rg-contoso-azure-local-gwc" --name "hybridaksextension" \
--extension-type Microsoft.HybridAKSOperator --release-train stable --version 7.2.12 \
--auto-upgrade False --config-file <path>\aks-extension-config.json --only-show-errors
returned error stream:
[ERROR: (ExtensionOperationFailed) The extension operation failed with the following error:
Failed to resolve the extension version from the given values.
InnerError: 'Extension type 'microsoft.hybridaksoperator' does not support release train 'stable' for version '7.2.12'.]
at Invoke-ArcHciAzCommandLine, ArcHci.psm1: line 3579
at Invoke-ArcHciAzCommand, ArcHci.psm1: line 3451
at Install-ArcHciHybridAKSExtension, ArcHci.psm1: line 4965
at Install-ArcHciHybridAKS, ArcHci.psm1: line 6723
at Install-ArcHciMgmt, ArcHci.psm1: line 6507
at DeployArbInternal, MocArbHelper.psm1: line 2006
at DeployArb, MocArbLifeCycleManager.psm1: line 312
Associated ARM Activity Log:
Code: NoRegisteredProviderFound
Message: The resource type 'clusters/networkProfiles' was not found in the provider namespace
'Microsoft.AzureStackHCI' for api version '2026-03-15-preview'.
Expected Behavior
- The Azure Arc Extension catalog must resolve
Microsoft.HybridAKSOperatorversion7.2.12on thestablerelease train for appliance cluster types. - The Azure Resource Provider
Microsoft.AzureStackHCIshould maintain backward-compatible registration forclusters/networkProfilesAPI versions (e.g.,2026-03-15-preview) that active production solution versions (12.2610.1004.50) actively depend on.
Suggested Remediation
- Azure Backend Fix: Re-register/enable API version
2026-03-15-previewforclusters/networkProfilesand align theMicrosoft.HybridAKSOperatorversion mapping forstable. - Deployment Package Update: Publish an updated ECE / Solution package aligning the deployment scripts to target the currently active
2026-11-01-previewAPI version and the corresponding extension release train.
Environment Details
- Product: Azure Local (Azure Stack HCI)
- OS Version: 2610
- Solution Version:
12.2610.1004.50 - Affected Regions: Confirmed in
Germany West Central; provider metadata indicates global scope across all Azure Local locations.
- 主要語言
- PowerShell
- 星號
- 82
- 分支
- 61
- 平均合併
- 1 小時 16 分鐘
- 30 天內合併 PR
- 9
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
Azure/AzureLocal-Supportability 的其他 Issue
-
難度 1/5 1-3 小時 新手友好度 88/100
Azure/AzureLocal-Supportability#290 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 82/100
Azure/AzureLocal-Supportability#289 ·
維護者通常 1 天內回覆
-
難度 3/5 1-2 天 新手友好度 48/100
Azure/AzureLocal-Supportability#369 ·
維護者通常 1 天內回覆
-
難度 5/5 一週以上 新手友好度 35/100
Azure/AzureLocal-Supportability#328 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 45/100
Azure/AzureLocal-Supportability#272 ·
維護者通常 1 天內回覆
查看 Azure/AzureLocal-Supportability 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 78/100
-
難度 2/5 1-3 小時 新手友好度 65/100
維護者通常 1 天內回覆
-
CRT transfer manager mutates the caller's ExtraArgs, so reusing the dict fails on the next upload未關閉
難度 2/5 1-3 小時 新手友好度 82/100
boto/s3transfer#433 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 72/100
-
S3 input fails in Docker image: DuckDB can't find home directory可能已有人在做 @jnioche 今天認領。 未關閉bug docker reporting
難度 2/5 1-3 小時 新手友好度 78/100
DigitalPebble/spruce#315 ·
維護者通常 1 天內回覆