Error: LCMVMSP10002 during upgrade to VCF Automation 9.x due to database size

Products

• VCF Automation

Issue/Introduction

Upgrade from Aria Automation 8.18.x to VCF Automation 9.x may fail if the underlying databases exceed a size that can be restored within the system's hard-coded timeout window. This issue is frequently observed in environments with active third-party integrations, such as Infoblox, which generate a high volume of historical action records.

Symptoms

• Upgrade from Aria Automation 8.18.x to VCF Automation 9.0.x fails during the product deployment phase
• Fleet Management displays the following error:
  

  Error Code: LCMVMSP10002
  Failed to deploy product on the application platform.
  Product deployment failed.

• Review of the vmsp-prelude-deployer pod logs reveals repeated restoration failures for specific databases:
  

  Restore failed for vro_gateway_db. Retrying in 10 seconds...
  Restore failed for abx_db. Retrying in 10 seconds...

• Database size checks reveal abx-db or vro-gateway-db exceeding 10–20 GB.
  

  kubectl exec -n prelude postgres-0 -- chpst -u postgres psql -c '\l+'

Environment

VMware Aria Automation 8.18.1

VCF Automation 9.0.x

Cause

The failure occurs because the abx-db and vro-gateway-db databases are too large to be restored within the 5-minute timeout window. The database footprint often grows due to the default 60-day historical data retention policy for ABX action runs, which can result in hundreds of thousands of entries in high-utilization environments.

Resolution

To resolve this issue, the database footprint must be reduced by adjusting historical data retention and performing a full vacuum before re-initiating the upgrade.

Because these steps require direct database manipulation engage a Broadcom Support for assistance citing the KB Article ID 443395.