vmware-trustmanagement service stopped after reboot

Products

• VMware Cloud Foundation

Issue/Introduction

After a reboot, some vCenter Server services may remain in a StartPending state. The vmware-trustmanagement service may be stopped and does not start automatically. As a result, the VMware Cloud Foundation Automation (VCFA) appliance may not be reachable and may fail to obtain the Management IP VIP.

Resolution

Verify and start vmware-trustmanagement service on vCenter Servers
1. Connect to both vCenter Servers (sa-m01-vc01 and sa-wld01-vc01) using SSH or Remmina.
2. Enter the appliance shell using the command: shell
3. Check service status using: service-control --status
4. Wait until no services remain in StartPending state.
5. If vmware-trustmanagement is stopped, start it using: service-control --start vmware-trustmanagement
Restore access to the VCFA appliance
6. Attempt to connect to the VCFA appliance sa-m01-vaa01.
7. If SSH fails, log in to the vSphere Client and locate VM sa-m01-vcfa-5k2pl.
8. Ensure the VM is fully powered off and then power it back on.
9. Verify that the VM has two IP addresses assigned in the Summary tab.
Validate Kubernetes pod health on the VCFA appliance
10. Switch to the root user using: sudo -i
11. Check pod status using: kubectl get pods -A | more
12. Wait until all pods are Running or Completed (up to 30 minutes).

Restart the k3s application
kubectl rollout restart deployment ccs-k3s-app -n prelude

Additional Information

• Do not manually start services while other services are in StartPending state.
• Restarting the VCFA appliance before vCenter services are fully started may cause repeated failures.
• Allow sufficient time for Kubernetes components to initialize before restarting workloads.