Preparing Cluster with Transport Node Profile Fails With This Operation Has a Different Version Than The Current System Version.

Products

• VMware NSX

Issue/Introduction

Symptoms:
When applying a Transport Node Profile to a cluster of unprepared ESXi hosts, the following error occurs:

"The object TransportNodeCollection/<UUID> used in this operation has different version 1 than the current system version. Fetch the latest copy of the object and retry operation. (Error code: 604)"

See Photo Below:



Hosts will remain in a 'not configured' state after this error is triggered.

Cause

There are four variables that must all be present in order to encounter this issue:

1) The profile has vmkernel adapter and/or physical NIC migration mapping in the Transport Node Profile

2) The TN profile is applied on a VC cluster in which some or all hosts are not TN. If all hosts in the cluster are already transport nodes, this issue will not occur. A host becomes a transport node once it has been prepared for NSX T.

3) There must be a host that is not the last one to become a transport and its validation fails. Validation can fail due to a powered-on VM on the host or a vmkernel adapter that's not found.

4) There must be another host that will become a TN and its validation passes (EX: A host in maintenance mode). If both a host that passes validation and a host that does not pass validation are present in the same cluster, it will trigger a version mismatch host-to-error map that's tracked for the cluster. 

Resolution

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.