Skip to content

DNS resolution fails for vCenter FQDN during the 1.8.0 upgrade #24

Description

@ParkerSDan

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions