VCFA Upgrade 9.0.2.0 -> 9.1.0.0 fails due to FQDN for VCF runtime services being in use
search cancel

VCFA Upgrade 9.0.2.0 -> 9.1.0.0 fails due to FQDN for VCF runtime services being in use

book

Article ID: 446799

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • Error:
    • One or more platform VIPs are already in use on the network. [com.broadcom.vcfa.upgrade.topology.check.test-topology-08b-platform-vip-available]
  • This Resolution is also listed:
    • The platform FQDN resolves to one or more VIPs that will be assigned to the new deployment. All resolved IP addresses must not be in use. Either free up the conflicting IP addresses or update DNS to point the platform FQDN to available IP addresses. Review <log-dir>/upgrade-precheck--test-topology-08b-platform-vip-available-<timestamp>.log on the source system for details, where <log-dir> is /var/log/vmware/prelude (8.x) or /tmp/vcfa-upgrade/logs (9.x).
  • In /tmp/vcfa-upgrade/logs we see such messages:
    • [INFO] Checking 1 IPs for availability (5 in parallel)
    • [DEBUG] Checking if IP #.#.#.# is available (timeout: 2s, ports: 443,80,22)
    • [DEBUG] IP #.#.#.# responded to arping - IP is in use
    • [WARNING] IP #.#.#.# is in use
    • [INFO] IP availability check complete: 0 available, 1 in use
    • [WARNING] Found 1 IP(s) in use: #.#.#.#
  • VCF Management Services' runtime services VM deployed in phase 3, a runtime services FQDN is needed in phase 4 for VCFA

Environment

  • VCF Operations 9.1 installation/upgrade
  • VCF Automation 9.1 installation/upgrade

Cause

The VCFA runtime services FQDN is separate from the VCF Management Services' runtime services FQDN

See this list of requirements for more details:  VCF Components FQDNs and IP addresses 

Resolution

Allocate another FQDN and IP address for the VCFA runtime services FQDN, following the requirements in  VCF Components FQDNs and IP addresses