Azure / Azure/AzureLocal-Supportability
update ARB VM and vm extensions inside of ARB VM - Kubeconfig can't be reached
- Lingua principale
- PowerShell
- Stelle
- 78
- Fork
- 60
- Merge medio
- 1g 6h
- PR unite (30g)
- 5
Descrizione
> **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**
When updating Azure Local to 10.2503.0.13 MocArb fails with cluster can't find kubernetes kubeconfig
**Repro steps**
Steps to reproduce the behavior:
Open powershell on a Cluster node: Start-SolutionUpdate -Id redmond/Solution10.2503.0.13
**Expected behavior**
Type 'UpdateArbAndExtensions' of Role 'MocArb' raised an exception: [UpgradeArbAndExtensions :arcappliance upgrade] Failed with Error C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\az.cmd arcappliance upgrade hci --config-file "C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\MocArb\WorkingDirectory\Appliance\hci-appliance.yaml" --only-show-errors returned a non empty error stream [ERROR: (PreUpgradeHealthValidationFailed) Pre Upgrade validation failed with error: "There was an error reaching to Kubernetes cluster with kubeconfig.
**Environment (please complete the following information):**
- Build 10.2503.0.13
- multi-node
- Production
- Region Westeurope
**Screenshots**

**Correlation ID**
ed24ecbf-ffee-4303-b5e4-0322c11ed3ec
**Additional context**
Update has worked on last 2 updates, but has failed with this build
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
No repository file, test, or entry point is named. Start by reproducing Start-SolutionUpdate with the provided build and reviewing the UpdateArbAndExtensions error, kubeconfig reachability failure, and correlation ID. Done would require a confirmed resolution for the Kubernetes kubeconfig failure during the Azure Local update.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- azure, kubernetes, powershell
- Ambito
- cloud, devops, infrastructure
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100