Aria Orchestrator vco-app pod fails to start with probe timeouts after installing Infoblox plugin 6.3

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

After installing or upgrading to the Infoblox plugin 6.3, the vco-app pod may fail to start, leading to a CrashLoopBackoff. When inspecting the vco-server-app.log, you will see entries indicating that the Git checkout process is taking an excessive amount of time, often exceeding 10 minutes:

DEBUG vco [...] com.vmware.o11n.git.StagingRepositoryService - Checkout took 656662ms

Environment

Aria Automation/Orchestrator 8.X

Cause

The vco-app pod has a defined timeout for its startup probes. If the Infoblox plugin causes the Git checkout operation to take longer than this timeout (as seen in the StagingRepositoryService logs), Kubernetes will kill the pod for being unresponsive, preventing the service from ever starting.

Resolution

To resolve this issue, you must disable the Infoblox plugin via the database to allow the Orchestrator service to start successfully.

1. SSH into the Aria Automation or Orchestrator appliance as root.

2. Access the database by running the following command:

   vracli dev psql vco-db
   

3. Disable the Infoblox plugin by executing this SQL statement:

   update vmo_plugin set enabled = FALSE where modulename = 'InfobloxIPAM';
   

4. Exit the PostgreSQL interface:

   \q
   

5. Restart the Orchestrator pod to apply the configuration:

   kubectl -n prelude delete pods -l app=vco-app
   

6. Once the pod restarts, it will bypass the Infoblox plugin loading process and should reach a Running state.