jstests/sharding/parallel.js creates 11 chunks for 10000 documents then attempts to distribute them across 3 shards by moving each to a random shard. It does so by manipulating strings, which map to the old naming convention for standalone shards. As of SERVER-32052, shards are replica sets, so these names don't match any shards, and each moveChunk fails (silently because the response is ignored).

This is probably related to the increasing number of NoProgessMade batch write failures in parallel.js, because the balancer is started before beginning a bulk insert and all 11 chunks are on one shard, leading to as many migrations as possible for this test setup.

The test should be updated to pick a random shard correctly, possibly by creating a new helper in ShardingTest.