SDDC Manager "Add Host" fails with error "No unassigned hosts available with storage type FC" due to NSX API invocation exception
search cancel

SDDC Manager "Add Host" fails with error "No unassigned hosts available with storage type FC" due to NSX API invocation exception

book

Article ID: 426978

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

The 'Add Host' operation in the SDDC Manager UI fails with the following error, which matches the symptoms described in KB 376808.

No unassigned hosts available with storage type FC. Commission hosts with physical NICs 0 &1 to Add Host from UI.

The following error is observed in /var/log/vmware/vcf/domainmanager/domainmanager.log:

<YYYY-MM-DD>T<HH:MM:SS> ERROR [vcf_dm,################################,####] [c.v.v.c.n.s.c.c.ComplexHelpers,dm-exec-10]  Exception occurred during NSX API invocation
java.util.concurrent.ExecutionException: com.vmware.vapi.std.errors.InvalidRequest: InvalidRequest (com.vmware.vapi.std.errors.invalid_request) => {
    messages = [],
    data = struct => {error_message=Certificate was revoked: [DhcpRelay, InternalIpSecVpnTunnelProfile, LbRule, DhcpProfile, StaticHopBfdPeer, LoadBalancerService, IpSecVpnLocalEndpointConfig, InternalSpoofGuardSwitchingProfile, LoadBalancerApplicationProfile, LogicalSwitch, LogicalRouter, NatRule, MetadataProxy, InternalRouteMapConfig, IpSecVpnPeerEndpointConfig, L2VpnSessionConfig, InternalMacManagementSwitchingProfile, RelayProfile, LogicalDhcpServer, Certificate, Group, IpSecVpnSessionConfig, InternalIpSecVpnDpdProfile, InternalQosSwitchingProfile, BgpNeighbor, LoadBalancerPersistenceProfile, InternalIpv6NdraProfileConfig, BaseHostSwitchProfile, InternalCommunityList, InternalPrefixListConfig, FirewallRule, InternalIpSecVpnIkeProfile, PolicyTransportZone, HostTransportNode, InternalIpv6DadProfileConfig, BgpNeighborInternalConfig]., httpStatus=BAD_REQUEST, error_code=2060, module_name=internal-framework},
    errorType = INVALID_REQUEST
}

Environment

  • SDDC Manager 5.x

Cause

A known issue in NSX.

Resolution

1. Perform a rolling restart of the 'manager' service across the three NSX Manager nodes. (Refer to Knowledge Base Article HTTP status 400 when running API calls to NSX for details)

restart service manager

2. Retry the 'Add Host' task, or follow the manual procedure outlined in the documentation: Add a Host to a vSphere Cluster Using the VMware Cloud Foundation API.