Cloud Proxy 9.1 deployment fails with error "Failed to start Wait for Network to be Configured"

Products

• VCF Operations

Issue/Introduction

When attempting to deploy Cloud Proxy (previously Aria Operations Cloud Proxy) version 9.1, the deployment fails.

• The virtual machine (VM) console displays the error: [FAILED] Failed to start Wait for Network to be Configured.
• The environment lacks a functional DNS server.

Environment

VCF Operations 9.1

VCF Operations Cloud Proxy 9.1

Cause

Cloud Proxy 9.1 requires a functional DNS infrastructure. During the initial network configuration phase, the deployment process attempts to resolve the system's FQDN. 

Broadcom documentation specifies that unique FQDNs and proper forward/reverse DNS resolution are mandatory for all VCF components.

Resolution

To resolve this issue, ensure the environment meets the networking prerequisites before re-deploying the Cloud Proxy.

1. Deploy a DNS Server: Ensure a DNS server is available and reachable within the environment.
2. Configure DNS Records: Create both Forward (A) and Reverse (PTR) DNS records for the Cloud Proxy’s static IP address and FQDN.
3. Update Existing Components: If other VCF components were previously deployed using only IP addresses, convert them to use FQDNs to ensure consistency across the environment.
4. Re-install Cloud Proxy: Delete the failed Cloud Proxy deployment and perform a fresh installation.

Additional Information

VCF requires unique FQDNs and static IP addresses for all VCF components, along with proper forward and reverse DNS resolution for each:

https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-1/planning-and-preparation/vcf-components-fqdns-and-ip-addresses.html

Deploy Cloud Proxy:

https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-1/deployment/upgrading-cloud-foundation/upgrade-backup-and-restore/configuring-cloud-proxies-in-vrealize-operations-cloud.html