TCA management cluster deployment fails due to DNS timeout
search cancel

TCA management cluster deployment fails due to DNS timeout

book

Article ID: 437701

calendar_today

Updated On:

Products

VMware Telco Cloud Automation

Issue/Introduction

Deployment of the management cluster fails during the provisioning phase. The UI and logs shows following error:

Unable to create cluster. Reason: Provision bootstrap cluster: timeout, stop polling progress of provisioning. Current state is VirtualMachineEntity bootstrap-hostname-master-xxx is at Provisioning phase, current message is fail to create VC client: Post "https://hostname/sdk": dial tcp: lookup hostname on hostIP:53: server misbehaving.Login to TCA-CP or Collect TechSupport Bundle of TCA-CP for the logs.

Environment

TCA 2.3

Cause

The DNS IP address of the TCA appliances was modified via the appliance management UI (port 9443) without executing a subsequent restart. The internal CoreDNS service of the temporary bootstrap cluster created by TCA-CP inherits its DNS configuration directly from the appliance. Consequently, the legacy DNS configuration persists, preventing the bootstrap cluster from resolving the vCenter Server hostname required to complete the provisioning sequence.

Resolution

  1. Validate all pending DNS IP modifications within the TCA appliance management UI (port 9443).
  2. Take snapshots for all TCA appliances (TCA-M and TCA-CPs) subjected to the DNS configuration changes.
  3. Perform a full restart of the affected TCA appliances to enforce OS-level network service updates.
  4. Retry the deployment workflow for the management cluster.