VIDB appliance fails to deploy from Offline Depot with error code LCMVSPHERECONFIG1000095
search cancel

VIDB appliance fails to deploy from Offline Depot with error code LCMVSPHERECONFIG1000095

book

Article ID: 410410

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite) VCF Operations

Issue/Introduction

  • Unable to deploy VIDB appliance on new VCF 9 instance using Offline Depot
  • VIDB appliance fails with error code LCMVSPHERECONFIG1000095
  • The /var/log/vrlcm/vmsp_bootstrap.log on the Fleet Management appliance shows the following

2025/09/04 14:33:19 Cleaning up local registry (package-registry) and kind cluster (kind-bootstrap)
>>> INIT0001 - Validating configuration
2025/09/04 14:33:19 role VCF Services Platform exists
2025/09/04 14:33:19 role VCF Services Platform Admin exists
successfully added global permissions for user xxx@domain
successfully added global permissions for user xxx@domain
2025/09/04 14:33:32 Validated number of IPs provided in IP Pools
2025/09/04 14:33:33 DNS resolution succeeded using nameserver xx.xx.xx.xx
>>> INIT0002 - Initializing bootstrap machine
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Loaded image: vmware/docker-registry:2.8.3
13944dd688fa3c35a99912bef9199fc9a38c0ea16198e16a17d03174795b2fe2
2025/09/04 14:33:36 Waiting for http://xx.xx.xx.xx:5000/v2/_catalog to be available
>>> INIT0003 - Deploying infrastructure components
2025/09/04 14:33:36 Push OCI components from xx-aa-bb-cc
2025/09/04 14:33:55 Installing package antrea-1.15.1-21.tzst
2025/09/04 14:33:56 Loading charts/antrea:1.15.1-4 into the registry
2025/09/04 14:33:57 Loading images/antrea-agent-photon:v1.15.1 into the registry
2025/09/04 14:33:57 Loading images/antrea-controller-ubuntu:v1.15.1 into the registry
2025/09/04 14:33:57 Loading images/antrea-ubuntu-simulator:v1.15.1 into the registry
2025/09/04 14:33:58 Installing package busybox-1.36.2-1.tzst
....
2025/09/04 14:37:01 Installing package velero-v1.13.2-3.tzst
Error: checksum mismatch, got: c5c1ac5f6a8267f83b4780650ea1dcec7c1523f29e70ea248f662b3ef984a7ff
2025/09/04 14:37:03 error: checksum mismatch, got: c5c1ac5f6a8267f83b4780650ea1dcec7c1523f29e70ea248f662b3ef984a7ff

  • The /var/log/vrlcm/vmware_vrlcm.log on the Fleet Management appliance shows

2025-09-04T14:33:18.955Z INFO vrlcm[1301] [pool-3-thread-32] [c.v.v.l.v.p.u.VMSPUtil] – VMSP Provisioning started
2025-09-04T14:37:03.618Z INFO vrlcm[1301] [pool-3-thread-32] [c.v.v.l.v.p.u.VMSPUtil] – VMSP Provisioning process exited with error code 1
2025-09-04T14:37:03.619Z INFO vrlcm[1301] [pool-3-thread-32] [c.v.v.l.v.p.u.VMSPUtil] – Fetching errors
2025-09-04T14:37:03.632Z INFO vrlcm[1301] [pool-3-thread-32] [c.v.v.l.v.p.u.VMSPUtil] – Capture errors exited with code :: 3
2025-09-04T14:37:03.632Z ERROR vrlcm[1301] [pool-3-thread-32] [c.v.v.l.v.p.t.BootstrapVMSPTask] – Failed to create services platform cluster. Refer to /var/log/vrlcm/vmsp_bootstrap_xxxxx.log for more details. 2025/09/04 14:33:36 Push OCI components from xx-aa-bb-cc
...
2025/09/04 14:37:01 Installing package velero-v1.13.2-3.tzst
Error: checksum mismatch, got: c5c1ac5f6a8267f83b4780650ea1dcec7c1523f29e70ea248f662b3ef984a7ff
2025/09/04 14:37:03 error: checksum mismatch, got: c5c1ac5f6a8267f83b4780650ea1dcec7c1523f29e70ea248f662b3ef984a7ff
ERR:INIT0003 - Deploying infrastructure components
at com.vmware.vrealize.lcm.vmsp.plugin.tasks.BootstrapVMSPTask.execute(BootstrapVMSPTask.java:108) [vmlcm-vmspplugin-core-9.0.0.0-SNAPSHOT.jar!/:?]
at com.vmware.vrealize.lcm.platform.automata.service.Task.retry(Task.java:158) [vmlcm-engineservice-core-9.0.0.0-SNAPSHOT.jar!/:?]
at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:60) [vmlcm-engineservice-core-9.0.0.0-SNAPSHOT.jar!/:?]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?]
at java.base/java.lang.Thread.run(Unknown Source) [?:?]

Environment

VCF 9.x

VIDB 9.x

Cause

This issue is caused by a corrupted package within the tar ball preventing the appliance from installing successfully

Resolution

Verify the SHA256 hash of the VIDB tar file to confirm it matches what is on the Broadcom website

Ensure your Offline Depot VM does not contain any snapshots while copying the VIDB tar file over to it. If it does, remove any snapshots from the Offline Depot VM and then copy the VIDB tar file over. After the VIDB tar file has been copied, re-sync the VIDB binary within the Fleet Management operations from VCF Operations admin UI