This is a test only issue due to the use of dassert.

In the moveChunk command, we expect the user to specify bounds for a hashed shard key. If we cannot find a chunk that matches these bounds, we throw an error. In that error message, though, we construct a ChunkRange from the min and max which were passed in via the command. The ChunkRange constructor contains a dassert that minkey must be less than max key, so if running in debug mode, we will hit an invariant rather than throwing the user assertion from the cluster command.

This can be fixed by printing the chunk range manually as we do earlier in the cluster command rather than creating a chunk range object.