The changes for SERVER-24467 tightened the checks around collection version mismatch in the moveChunk command. However, this breaks the initial partitioning of a hashed sharded collection by a 3.2 mongos, because 3.2 it does not refresh the collection metadata between iterations.

In order to preserve backwards compatibility with 3.2 we should remove the exact collection version check.