Adding an ESXi Host to a Workload Domain cluster fails with a "500 Internal Server Error" while resolving NSX host preparation issues.

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:

• Adding a host to a WLD cluster fails during NSX-V host preparation. In NSX vsm.log, similar messages may be seen:
  
  2019-06-22 05:29:47.814 GMT ERROR http-nio-127.0.0.1-7441-exec-1 BaseRestController:521 - - [nsxv@6876 comp="nsx-manager" level="ERROR" subcomp="manager"] REST API failed : 'Index: 0, Size: 0'
  java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
          at java.util.ArrayList.rangeCheck(ArrayList.java:657) ~[?:1.8.0_202]
          at java.util.ArrayList.get(ArrayList.java:433) ~[?:1.8.0_202]
          at com.vmware.vshield.vsm.fabric.agent.service.impl.AgentServiceImpl.getAgentIdByServiceAndHostId_aroundBody76(AgentServiceImpl.java:386) ~[vsphere-1.0.jar:?]
          at com.vmware.vshield.vsm.fabric.agent.service.impl.AgentServiceImpl$AjcClosure77.run(AgentServiceImpl.java:1) ~[vsphere-1.0.jar:?]
          at org.springframework.transaction.aspectj.AbstractTransactionAspect.ajc$around$org_springframework_transaction_aspectj_AbstractTransactionAspect$1$2a73e96cproceed(AbstractTransactionAspect.aj:66) ~[spring-aspects-5.1.4.RELEASE.jar:5.1.4.RELEASE]
          at org.springframework.transaction.aspectj.AbstractTransactionAspect$AbstractTransactionAspect$1.proceedWithInvocation(AbstractTransactionAspect.aj:72) ~[spring-aspects-5.1.4.RELEASE.jar:5.1.4.RELEASE]
          at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:294) ~[spring-tx-5.1.4.RELEASE.jar:5.1.4.RELEASE]
          at org.springframework.transaction.aspectj.AbstractTransactionAspect.ajc$around$org_springframework_transaction_aspectj_AbstractTransactionAspect$1$2a73e96c(AbstractTransactionAspect.aj:70) ~[spring-aspects-5.1.4.RELEASE.jar:5.1.4.RELEASE]
          at com.vmware.vshield.vsm.fabric.agent.service.impl.AgentServiceImpl.getAgentIdByServiceAndHostId(AgentServiceImpl.java:376) ~[vsphere-1.0.jar:?]
          at com.vmware.vshield.vsm.nwfabric.service.impl.FabricDeployerImpl.getAgentIdFromHostId(FabricDeployerImpl.java:324) ~[vsphere-1.0.jar:?]
          at com.vmware.vshield.vsm.nwfabric.service.impl.FabricDeployerImpl.resolveIssues(FabricDeployerImpl.java:345) ~[vsphere-1.0.jar:?]
          at com.vmware.vshield.vsm.nwfabric.service.impl.NetworkPrepServiceImpl.resolveIssues_aroundBody10(NetworkPrepServiceImpl.java:243) ~[vsphere-1.0.jar:?]
          at com.vmware.vshield.vsm.nwfabric.service.impl.NetworkPrepServiceImpl$AjcClosure11.run(NetworkPrepServiceImpl.java:1) ~[vsphere-1.0.jar:?]
          at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149) ~[aspectjweaver-1.8.9.jar:1.8.9]
          at com.vmware.vshield.vsm.aspects.security.VsmSecuredAspect.secureCheck(VsmSecuredAspect.java:134) ~[vsm-core-1.0.jar:?]
          at 

Note:The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware Cloud Foundation 3.7.x

Resolution

This is a known issue, that is still under investigation by VMware. 

Workaround:
To workaround this issue, restart the add host workflow.