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

Products

• VCF Operations

Issue/Introduction

vIDB Component Deployment Failure

While attempting to deploy the Identity Broker (vIDB) as a separate appliance within VMware Cloud Foundation (VCF) Operations, the deployment process fails with the following UI error:

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

Error code: LCMVIDB0002  
No failed pods found.

In the Fleet Manager Lifecycle Manager deployment status UI, the following exception is observed:

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)

VCF Automation Component Deployment Failure

During the deployment of the VCF Automation component, the following exception is encountered:

com.vmware.vrealize.lcm.vmsp.common.exception.DeploymentFailedException: No failed pods found.

Additionally, the deployment logs indicate that certain pods remain stuck in the initialization phase:

-- FAILED POD [prelude/tenant-manager-0] --
Error from server (BadRequest): container "app" in pod "tenant-manager-0" is waiting to start: PodInitializing

-- FAILED POD [prelude/vcfa-service-manager-xxxxxxxxx-xxxxxxxxx] --
Error from server (BadRequest): container "manager" in pod "vcfa-service-manager-xxxxxxxxx-xxxxxxxxx" is waiting to start: PodInitializing

This issue prevents successful deployment of the vIDB and VCF Automation components, with pods remaining in a non-ready state despite the system reporting no failed pods.

Environment

VCF Operations 9.0, vIDB 9.0 & VCF Automation 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.

• Delete the existing Fleet Manager Appliance Power off and delete the improperly configured Fleet Manager appliance from the vCenter inventory.
  
  
• 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.
  
  
• Retry Identity Broker Deployment: Once the Fleet Manager is online and reachable via FQDN, attempt the Identity Broker deployment again.