Identity Broker Deployment Failure

Products

• VCF Operations

Issue/Introduction

You are attempting to deploy the Identity Broker as a separate appliance.  The deployment is failing in VCF 9.0

Environment

VCF Operations 9.0

Cause

During the deployment of the Fleet Manager, short name was used in the host name field instead of Full Qualified Domain name (FQDN).

The following error is observed in Fleet Manager Lifecycle Manager deployment status:

com.vmware.vrealize.lcm.common.exception.EngineException: No failed pods found.No failed pods found.    at com.vmware.vrealize.lcm.plugins.vidb.core.task.deploy.DeployVidbOnVMSPTask.execute(DeployVidbOnVMSPTask.java:89)    at com.vmware.vrealize.lcm.plugins.vidb.core.task.deploy.DeployVidbOnVMSPTask.retry(DeployVidbOnVMSPTask.java:123)    at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:60)    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

Resolution

Redeploy the Fleet Manager in VCF 9.0 via following Broadcom Technical Document Deploy the VCF Operations fleet management Appliance.

Ensure the Hostname field is entered with the FQDN, as noted in section 4b of the deployment guide.

• Hostname. Do not include nonstandard characters such as underscores (_) in node names. Always use the FQDN.