Host Stuck in Decommissioning Status in SDDC Manager When Removing Host from NSX Cluster
search cancel

Host Stuck in Decommissioning Status in SDDC Manager When Removing Host from NSX Cluster

book

Article ID: 414493

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

Occasionally a host may become stuck in a 'Decommissioning' state in SDDC Manager when attempting to remove the host from an NSX cluster. 

Environment

SDDC Manager 5.x

Cause

The host does not contain the transport_node value assigned by NSX Manager. Typically this occurs when the host is removed from NSX Manager directly which is an out of band management change. When this occurs:

  • We see the following failure in the SDDC Manager Tasks:
Description Delete Transport Node Configuration from ESXi Host(s)
Progress Messages Transport node deletion operation failed

Error

Message: Transport node deletion operation failed

Remediation Message:

Reference Token: #######

Cause: Required operation parameter 'host_transport_node_id' is missing Required operation parameter 'host_transport_node_id' is missing

 

  • Operationsmanager.log will indicate a failure with the following back-trace:

Exception occurred during NSX API invocation
java.util.concurrent.ExecutionException: com.vmware.vapi.client.exception.BindingsException: Required operation parameter 'host_transport_node_id' is missing

Resolution

Contact the Broadcom VCF Support team to perform the necessary Database Entry deletion steps to remove the host from your SDDC Manager's Database. 

This often requires VMware Technical Support to have a live call with the customer to properly resolve this issue.  A log bundle from SDDC Manager can help with the process - How to collect SDDC Manager Logs.