VCF Operations Orchestrator deployment fails due to short hostname

Products

• VCF Operations

Issue/Introduction

During the deployment of the VCF Operations Orchestrator appliance, the firstboot initialization process fails and times out.

The console may display the following error:
[FAILED] Failed to start Run firstboot or everyboot script.

The /var/log/bootstrap/firstboot.log file contains errors similar to:

Waiting for infrastructure services...
+ /opt/scripts/wait-k8s-up -t 600 local-infra
Waiting for local-infra timed out: curl: (6) Could not resolve host: <short hostname>
YYYY-mm-dd HH:MM:SSZ Script /etc/bootstrap/firstboot.d/02-setup-kubernetes failed, error status 1

Environment

VCF Operations Orchestrator 9.x

Cause

This issue occurs when a short hostname (e.g., o11n) is entered instead of a Fully Qualified Domain Name (FQDN) (e.g., o11n.example.com) during the OVA/OVF deployment wizard.

Resolution

To resolve this issue, delete the failed appliance and redeploy.

1. Delete the failed deployment instance from the inventory.
2. Initiate a new deployment via the OVF deployment wizard.
3. Ensure that the Hostname parameter is configured with a valid, fully qualified domain name (e.g., o11n.example.com).