Unable to upgrade Azure Arc Resource Bridge on VMware after moving datastores

Open
#23 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
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
azure
Domain
cloud, infrastructure

Research direction

Start by reproducing the v1.6.0-to-v1.7.0 upgrade after moving the Azure Arc Resource Bridge from the deleted vVol datastore to the VMFS 6 datastore. Inspect the edited .yaml and the later upgrade step for remaining references to the old datastore name. Done means the upgrade completes without referencing the deleted datastore.

Written by the indexing model from the issue text.

Description

When upgrading from v1.6.0 to v1.7.0, an error was thrown regarding our datastore. Looking into it, the AARB was originally installed on a vVol datastore, then later moved to a newer VMFS 6 datastore. The vVol datastore was deleted this year. I edited the .yaml file to replace the old datastore name with the new one, re-ran the upgrade and it got further, but then still appeared to reference the old datastore name later in the upgrade process and I was unable to proceed. I ended up deleting the AARB and creating a new one.

Dominant language
No language data
Stars
4
Forks
10
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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/ArcResourceBridge

All issues in Azure/ArcResourceBridge

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.