Error "Error: Platform config fault reported by vCenter Server. Platform Config fault occurred. An error occurred during host configuration. vCenter Server task (moref: task-#######) failed in vCenter Server" while powering on a Virtual Machine

Products

• VMware Cloud Director

Issue/Introduction

• Power on operation of a virtual machine  in vCloud director fails.
• The below error message is observed during the failure 
  
  Error:  Platform config fault reported by vCenter Server. Platform Config fault occurred. An error occurred during host configuration. vCenter Server task (moref: task-#######) failed in vCenter Server

Environment

10.4.3

Cause

• The error "Platform config fault reported by vCenter Server" typically indicates a communication or state synchronization failure between VMware Cloud Director (VCD), vCenter Server, and NSX (specifically the NSX Host Transport Node status).
  
  
• This is an issue at the underlying vSphere Infrastructure layer either at vCenter Server, ESXi host, or with NSX.
  
  
• The most common drivers are:

  1. NSX Operations Agent Failure: The nsx-opsagent on the ESXi host is stopped or hung, preventing vCenter from pushing networking configurations requested by VCD.

  2. Certificate Mismatch: A recent change in SSL certificates (vCenter or NSX) hasn't been fully propagated, causing the "Host Config RPC" to fail.

  3. Host Transport Node State: The host is in a "Partial Success" or "Failed" state within the NSX Manager UI.

Resolution

Follow these steps to diagnose and resolve the host-level configuration fault:

1. Identify the Impacted Host

   Locate the specific ESXi host where the VCD task failed by checking the vCenter Server Tasks and Events. Look for the task-####### mentioned in the VCD error message to identify the specific host being configured.

2. Restart NSX Agents on ESXi

   If the host is managed by NSX, log in to the impacted ESXi host via SSH and restart the management agents:
   

   1. Check status of the NSX Ops Agent
      
      /etc/init.d/nsx-opsagent status
      
      
   2. Restart the NSX Ops Agent
      
      /etc/init.d/nsx-opsagent restart
      
      
   3. Restart the NSX Proxy Agent
      
       /etc/init.d/nsx-proxy restart
      
      
3. Verify Host Transport Node Status
   
   
   1. Log in to the NSX Manager UI.
   2. Navigate to System > Fabric > Nodes > Host Transport Nodes.
   3. Locate the impacted host and check the Configuration State.
   4. If the state is Failed, click Resolve or Re-set State.
      
      
4. Validate Certificates
   
   
   1. If the error persists, ensure that the vCenter registration in VCD and the NSX Manager connection are healthy:
   2. In VCD, go to Resources > Infrastructure Resources > vCenters. Select the vCenter and click Refresh/Reconnect.
   3. Accept any prompted certificate updates.
      
      
5. Verify there are no errors and certificates are up to date between NSX, vCenter, and ESXi following:
   
   Host Transport Nodes in Install Failed state with error "Failed to send HostConfig RPC to MPA" and "Certificate validation failed: 18-self signed certificate"
   
   
6. Check the vpxd.log in vCenter Server and syslog.log in the NSX Manager to identify what exactly is the cause of the issue.