DNS resolution fails for vCenter FQDN during the 1.8.0 upgrade

Open
#24 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
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Domain
networking

Research direction

Reproduce the upgrade from 1.7.0 to 1.8.0 using the vCenter FQDN, then compare the DNS server selected during the upgrade with the server specified in the .yaml file. The issue is done when the configured DNS server resolves the vCenter FQDN and the upgrade completes without requiring the vCenter IP address.

Written by the indexing model from the issue text.

Description

After building a new AARB following the change of datastore issue, I upgraded it from 1.5.0 to 1.6.0 successfully, then to 1.7.0 successfully.

I was then not able to upgrade any further due to what appears to be a DNS issue in the 1.8.0 upgrade process. I was seeing errors relating to not being able to resolve the FQDN of our vCenter server (which does not use .local).

It seems it was using a different DNS server (10.96.0.10) to what was in the .yaml file, and to what the previous successful upgrades had used.

Re-running the upgrade, but entering the IP address of vCenter, worked.

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 Networking issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.