Postgres pods stuck in 0/1 running state due to abx_db bloat in Aria Automation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• The Postgres pods fail to start, remaining in a 0/1 Running state and continuously restart.
• Database replication initiates but times out and is terminated after the database size reaches a size
• /opt/scripts/deploy.sh script runs for very long time or times out while trying to start postgres pods.

Environment

VMware Aria Automation 8.18.1

Cause

The issue is caused by massive data bloat in the abx_db. The public.abx_action_content table retains orphaned rows and an excessive number action versions which are not being used, swelling the database size. The Postgres startup probe times out before the massive data replication can successfully complete

Resolution

Database modifications are required to remove orphaned rows and actions. To resolve this issue, please open a Support Request with Broadcom Technical Support and note this Article ID (444103) in the problem description. For more information, see Creating and managing Broadcom support cases.

Additional Information