Cloud Builder fails to validate JSON during bringup with error: No matching cluster found with prefix in vCenter

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:

• You see messages similar to the following in the /opt/vmware/bringup/logs/vcf-bringup-debug.log file on the Cloud Builder VM:

2019-04-29T17:06:12.491+0000 [bringup-app-ems,[1a603c2b8e4bfef1,56f1]] DEBUG [c.v.e.s.b.a.r.v.BringupRestInputValidatorVxRail,http-nio-127.0.0.1-9080-exec-6] Get validation with ID f6cb5a4e-####-####-####-##########63
2019-04-29T17:06:15.826+0000 [bringup-app-ems,[45caed71ed70a4cf,9791]] ERROR [c.v.e.s.c.c.v.vsphere.VsphereClient,SimpleAsyncTaskExecutor-1] Failed to connect to https://10.176.50.217/sdk
java.util.concurrent.ExecutionException: (vim.fault.InvalidLogin) {
faultCause = null,
faultMessage = null
}

 

Caused by: com.vmware.vim.binding.vim.fault.InvalidLogin: Cannot complete login due to an incorrect user name or password.
 
2019-04-29T17:06:15.832+0000 [bringup-app-ems,[45caed71ed70a4cf,9791]] WARN [c.v.v.v.c.h.i.HttpConfigurationCompilerBase$ConnectionMonitorThreadBase,SimpleAsyncTaskExecutor-1] Shutting down the connection monitor.
2019-04-29T17:06:15.832+0000 [bringup-app-ems,[0000000000000000,0000]] WARN [c.v.v.v.c.h.i.HttpConfigurationCompilerBase$ConnectionMonitorThreadBase,VLSI-client-connection-monitor-2] Interrupted, no more connection pool cleanups will be performed.
2019-04-29T17:06:15.832+0000 [bringup-app-ems,[45caed71ed70a4cf,9791]] ERROR [c.v.e.s.c.c.v.vsphere.VcManagerBase,SimpleAsyncTaskExecutor-1] Failed (vim.fault.InvalidLogin) {
faultCause = null,
faultMessage = null
}

• You see messages similar to the following in the /var/log/vmware/sso/vmware-identity-sts.log file on the PSC VM:

[2019-04-29T19:54:06.983Z tomcat-http--8 vsphere.local db41e81c-####-####-####-#########1a WARN com.vmware.identity.idm.server.provider.vmwdirectory.VMwareDirectoryProvider] The user is SRP-enabled and failed to authenticate.
[2019-04-29T19:54:06.983Z tomcat-http--8 vsphere.local db41e81c-####-####-####-#########1a ERROR com.vmware.identity.idm.server.IdentityManager] Failed to authenticate principal [[email protected]] for tenant [vsphere.local]
Caused by: com.vmware.identity.interop.ldap.InvalidCredentialsLdapException: Invalid credentials

 

Note:  Symptoms and log entries above are examples only.  Dates, timestamps and names will vary across customer environments.

Environment

VMware Cloud Foundation 3.7.x
VMware Cloud Foundation 2.x

Resolution

This issue is resolved in VMware Cloud Foundation 3.7.2

Workaround:
If restarting the deployment with 3.7.1, the following workardound can be used:

1. Change the vCenter Server and PSC(s) root passwords to be the same password as the SSO password in the excel validation file. Optionally, these passwords can be changed in JSON file created from the excel validation file. Use the steps noted in How to reset the lost or forgotten root password in vCenter Server Appliance 6.5 (2147144) to change the root passwords on the vCenter Server and PSC(s).
2. Restart the validation task.