Azure / Azure/AzureLocal-Supportability
Bug: Azure Local / Azure Arc Onboarding Stuck – Private Link Scope Network Error
- Langage dominant
- PowerShell
- Étoiles
- 78
- Forks
- 60
- Merge moyen
- 1 j 6 h
- PR mergées (30 j)
- 5
Description
> **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**
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Reproduire l’onboarding de Azure Local / Azure Arc jusqu’à la vérification de Private Link Scope et inspecter C:\\ProgramData\\AzureConnectedMachineAgent\\Log\\himds.log pour rechercher l’échec AZCM0026. Déterminer si un scope dans un autre abonnement est pris en charge ou doit être ignoré ; c’est terminé lorsque l’onboarding s’achève sans cette erreur réseau.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- azure
- Domaine
- cloud, infrastructure
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100