Error; INIT0003 - Deploying infrastructure components received if Fleet Manager while deploying vIDB

Products

• VCF Operations

Issue/Introduction

When attempting to deploy the identity broker (vIDB) via fleet manager on VMware Cloud Foundation (VCF) in a dark site (air-gapped) environment, the deployment fails during the "Deploying infrastructure components" phase. The deployment fails with an INIT0003 error, specifically returning the following message:

INIT0003 error, specifically stating: ERROR: failed to create cluster: failed to pull image "registry.vmsp-platform.svc.cluster.local:5000/images/kindest-node:v1.32.8": command "docker pull registry.vmsp-platform.svc.cluster.local:5000/images/kindest-node:v1.32.8" failed with error: exit status 1

Environment

• VCF Cloud Foundation 9.0.2
• Identity Broker 9.0.2

Cause

An incorrect or newer version of the vIDB binary is side-loaded onto the Fleet Management appliance. In air-gapped environments requiring manual staging, an incompatible binary prevents the system from extracting the required OCI components and manifests, resulting in a manifest unknown error.

Resolution

1. Access the fleet appliance and check the file currently copied to the '/data/PROD/COMP/VIDB' folder.

2. Identify the file that is present (vidb-external-9.0.2.0.25084325.tar).

3. Re -download the correct version (9.0.2.0) and copy it to the '/data/PROD/COMP/VIDB' directory on the fleet appliance.

4. Confirm the integrity of the file by running the following command:

   sha256sum vidb-external-9.0.2.0.25084325.tar

5. Ensure the output matches the expected checksum from the VMware Cloud Foundation Downloads page in Broadcom Support Portal.
   
   
6. Navigate to the Binary Management page once the checksum is validated, download the correct binary, and proceed with the installation.