update ARB VM and vm extensions inside of ARB VM - Kubeconfig can't be reached
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure, kubernetes, powershell
- Domain
- cloud, devops, infrastructure
Research direction
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.
Written by the indexing model from the issue text.
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
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
- Dominant language
- PowerShell
- Stars
- 78
- Forks
- 60
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/AzureLocal-Supportability
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Azure/AzureLocal-Supportability#253 · 1 comment ·
All issues in Azure/AzureLocal-Supportability
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
bug needs-triage service/elbv2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hashicorp/terraform-provider-aws#50100 · 1 comment ·