Identity Broker deployment fails with error "LCMVIDB0002 No failed pods found" in VCF Operations

Products

• VCF Operations

Issue/Introduction

• While attempting to deploy the Identity Broker as a separate appliance  in VMware Cloud Foundation (VCF) Operations, the deployment fails with below UI Error:

  Error code: LCMVIDB0002
   
  LCMVIDB0002
   
  No failed pods found. No failed pods found.

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

  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)

 

Environment

VCF Operations 9.0

Cause

This issue occurs because the Fleet Manager appliance was deployed using a Short Name instead of a Fully Qualified Domain Name (FQDN).

The Identity Broker installation process relies on FQDN resolution to correctly locate and communicate with the Fleet Manager appliance. When only a short name is provided, this resolution fails, resulting in the "No failed pods found" error during the deployment task

Resolution

To resolve this issue, the VCF Operations Fleet Manager appliance must be redeployed using the correct FQDN format.

 

 

1. Delete the existing Fleet Manager Appliance Power off and delete the improperly configured Fleet Manager appliance from the vCenter inventory.
2. Redeploy Fleet Manager - Refer Deploy the VCF Operations fleet management Appliance
   
   Note:
   In the deployment wizard, ensure the Hostname field is populated with the FQDN (e.g., fleetmanager.cexample.com), not the Short Name. Do not include non-standard characters such as underscores (_) in node names.
3. Retry Identity Broker Deployment: Once the Fleet Manager is online and reachable via FQDN, attempt the Identity Broker deployment again.