Azure / Azure/AzureLocal-Supportability
Bug: Azure Local / Azure Arc Onboarding Stuck – Private Link Scope Network Error
- Lenguaje dominante
- PowerShell
- Estrellas
- 78
- Forks
- 60
- Merge medio
- 1 d 6 h
- PR fusionados (30 d)
- 5
Descripción
> **IMPORTANT**: Do not share any personal data in the bug report. This repository is a public forum and this report will also be public.
**Bug description**
I am trying to onboard Azure Local on Azure Arc. The onboarding process gets stuck with the following error message:
```
No indication of Private Link Scope but found private endpoint agentserviceapi.guestconfiguration.azure.com: *.*.*.*
It appears that the process is expecting a Private Link Scope, but the existing scope is deployed in another subscription. This prevents the onboarding from completing.
INFO AZCM0026: Network Error
```
**Repro steps**
Steps to reproduce the behavior:
Start onboarding Azure Local / Azure Stack HCI to Azure Arc.
Follow the onboarding steps until the process checks for Private Link Scope.
Observe that it fails with the above network error.
**Expected behavior**
The onboarding should not ask for a Private Link Scope if the scope is in a different subscription. The process should either:
Allow cross-subscription scopes, or
Skip the Private Link requirement when no scope exists in the current subscription.
**Environment (please complete the following information):**
Agent Version : 1.55.03132.2414
Agent Logfile : C:\ProgramData\AzureConnectedMachineAgent\Log\himds.log
Agent Status : Disconnected
Agent Last Heartbeat :
Agent Error Code :
Agent Error Details :
Agent Error Timestamp :
Using HTTPS Proxy :
Proxy Bypass List :
Upstream Proxy :
Gateway URL :
Cloud Provider : AzSHCI
Cloud Metadata
Manufacturer : HPE
Model : ProLiant DL380 Gen10 Plus
**Screenshots**
Guía de contribución
Línea de trabajo
Reproducir el onboarding de Azure Local / Azure Arc hasta la comprobación de Private Link Scope e inspeccionar C:\\ProgramData\\AzureConnectedMachineAgent\\Log\\himds.log en busca del error AZCM0026. Determinar si se admite un scope en otra suscripción o si debe omitirse; se considera completado cuando el onboarding finaliza sin este error de red.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- azure
- Área
- cloud, infrastructure
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100