To resolve this issue, you must ensure the VCF Automation services are running correctly before retrying the upgrade:
1. Log in to the VCF Automation appliance as root via SSH as vmware-system-user and then switch to root by executing following command:
su -u
2. Verify the status of the pods by running the following commands:
kubectl get pods -n prelude
kubectl get pods -A
3. If any pods are in a CrashLoopBackOff, Error, or Pending state, troubleshoot the Automation appliance to restore service health. You may open a
Broadcom Support Case with VCF Automation team for the same.
4. Once all VCF Automation services are confirmed to be healthy and the UI is accessible, return to the upgrade interface and Retry the inventory sync or upgrade task.