When executing a status check command (e.g., vracli vro info) immediately after an update or appliance reboot of Aria Automation Orchestrator, the following error message is output and the process fails:
Could not load plugin metadata from pluginsVersionData
VMware Aria Automation Orchestrator 8.x
This issue occurs when a CLI command is executed before the startup and initialization of the internal Kubernetes pods are complete following an appliance reboot.
If the system information retrieval process is executed while dependent services are not fully started, it fails to load the plugin metadata and terminates with an error.
Note: For reboots associated with an update, it may take 1 hour or more for all components to complete their startup sequence.
Wait until the system initialization is complete and all services are in a running state.
root user.prelude namespace:kubectl -n prelude get pods
Example:# kubectl -n prelude get podsNAME READY STATUS RESTARTS AGEcontour-contour-#########-##### 1/1 Running 0 MmSSscontour-envoy-##### 2/2 Running 0 MmSSsorchestration-ui-app-##########-##### 1/1 Running 0 MmSSspostgres-0 1/1 Running 0 MmSSsproxy-service-##########-##### 1/1 Running 0 MmSSsvco-app-##########-##### 2/2 Running 0 MmSSsSTATUS of all pods becomes Running.Running state, execute the intended command (e.g., vracli vro info) again to verify that it processes successfully.