This is a known issue effecting NSX T. This issue will be fixed in a future version of NSX T.
Workaround:
There are two primary workarounds for this issue:
1.) You may detached the transport node profile from the vCenter Cluster. Place one ESXi host into vCenter maintenance mode. This host will be installed with NSX T. Then, re-attach the transport node profile to the cluster. This will install a single ESXi host per iteration.
2.) You may remove the vmkernel adapter and/or physical NIC migration mapping in the Transport Node Profile for initial NSX T VIB install. Then, once all hosts are installed, add the desired vmkernel adapter and/or physical NIC migration mapping into the Transport Node Profile which will trigger this configuration change across the cluster once all transport nodes are already installed.