update ARB VM and vm extensions inside of ARB VM - Kubeconfig can't be reached

Open
#79 0 comments 0 reactions 0 assignees View on GitHub

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

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

Image

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/AzureLocal-Supportability

All issues in Azure/AzureLocal-Supportability

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.