VMware Cloud Foundation operations may break if any resource has a hostname with less than 3 labels (i.e., 'abc.vmw.com' is permitted, but 'vmw.com' is not)
search cancel

VMware Cloud Foundation operations may break if any resource has a hostname with less than 3 labels (i.e., 'abc.vmw.com' is permitted, but 'vmw.com' is not)

book

Article ID: 318234

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

Symptoms:
Various Bringup will fail at validation.
Most operations that communicate with VMware Cloud Foundation LCM process will fail.
In LCM or Bringup logs you will see a stack trace like:

Caused by: java.lang.RuntimeException: [address] some.hostname:Validation failed. FQDN value does not match valid FQDN pattern
 at sun.reflect.GeneratedConstructorAccessor184.newInstance(Unknown Source)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
 at com.vmware.vcf.shared.ValidationHelper.validateAndThrowOnFailureUsingException(ValidationHelper.java:101)
 at com.vmware.evo.sddc.common.plugin.model.contract.RemoteEndpoint.validate(RemoteEndpoint.java:68)
 at com.vmware.evo.sddc.common.plugin.model.contract.RemoteEndpoint.<init>(RemoteEndpoint.java:41)
 at com.vmware.evo.sddc.common.plugin.model.contract.RemoteEndpoint$RemoteEndpointBuilder.build(RemoteEndpoint.java:20)
 at com.vmware.evo.sddc.common.plugin.model.contract.RemoteEndpoint$1.build(RemoteEndpoint.java:55)
 at


Environment

VMware Cloud Foundation 4.2

Resolution

This issue is fixed in VCF 4.3

Workaround:
To workaround this issue, please follow the below:
  • Pre-bringup: change the hostnames of all ESXi hosts to have 3 or more labels in their fully-qualified domain names.
  • On a brownfield upgraded setup: none - update to 4.3 or later.