Using uppercase in the ESXi FQDNs for Management Cluster will cause the Bringup workflow to fail
search cancel

Using uppercase in the ESXi FQDNs for Management Cluster will cause the Bringup workflow to fail

book

Article ID: 325208

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

Symptoms:
  • If the ESXi FQDNs are in uppercase for the Management Cluster in the Bringup parameter sheet or json.
  • The "Restore Lockdown Mode on ESXi Hosts" task fails during Bringup.


Environment

VMware Cloud Foundation 4.x

Resolution

This issue is resolved in VCF 4.1.

Workaround:
To workaround the issue follow the steps below along with re-imaging the host and starting a new Bringup workflow:
  1. Download the attached ManagementClusterConfiguration.json file.
  2. Take a backup/ snapshot of the Cloud Builder VM. 
  3. Using a file transfer utility, replace the /opt/vmware/bringup/webapps/bringup-app/conf/workflowconfig/ems_recipes/ManagementClusterConfiguration.json file with the downloaded ManagementClusterConfiguration.json on the Cloud Builder VM.
  4. Start the Bringup workflow in the Cloud Builder UI


Additional Information

Impact/Risks:
As the vCenter Server inventory will automatically add the ESXi FQDNs as lowercase, there is a mismatch between the uppercase value in VMware Cloud Foundation and vCenter.

Attachments

ManagementClusterConfiguration get_app