VCF Operations License server deployment fails during license validation when IPv6 Preferred is set to true

Products

• VCF Operations

Issue/Introduction

Deployment of VCF Operations License server VM fails during the license verification phase.

The deployment sequence halts with the status "VCF Ops Host Not configured" when deploying from OVA.

Logs and system checks reveal:

• CASA database script /storage/db/casa/webapp/hsqldb/casa.db.script shows the node bound to an IPv6 address.
• Communication fails even if /etc/hosts contains correct IPv4 mappings.
• The License Installer cannot establish a connection to the licensing backend.

Environment

VMware Cloud Foundation (VCF) 9.1.0.0100

Cause

• The failure occurs when IPv6 Preferred? is enabled in vCenter vApp Options and the option to use Fully Qualified Domain Name (FQDN) as default was omitted during OVF deployment.
• Under these conditions, the CASA service defaults to IPv6 bindings. Since the License Server currently supports communication over IPv4 only the validation fails.

Resolution

This behavior is a known issue in VMware Cloud Foundation 9.1.
Fixed in release 9.1.1 and higher. See Download Broadcom products and software for steps to download this release.

If immediate remediation is required, use one of the following methods:

Method 1: Modify vApp Options

1. Log in to VCF Operations Admin UI
2. Take the cluster offline
3. Power off the VCF Operations virtual machine.
4. Navigate to vCenter > Configure > vApp Options.
5. Set IPv6 Preferred? to False.
6. Power on the virtual machine and verify service binding.

Method 2: Redeploy with FQDN (Recommended)

1. Perform a new deployment of the VCF Operations OVA.
2. In the deployment wizard, select FQDN as default.
3. Ensure valid A and PTR records exist in DNS for the appliance. This allows the installer to resolve via DNS and successfully fall back to IPv4.

Additional Information

Subscribe to this article for updates on fix status.