Azure / Azure/ArcResourceBridge
DNS resolution fails for vCenter FQDN during the 1.8.0 upgrade
Open
- Dominant language
- No language data
- Stars
- 4
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
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.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.