If running in a config shard suite, it's possible that the configsvr is the donor shard that migration_coordinator_failover_include.js forces a failover on. Some of the test cases in this test set a failpoint migrationCommitVersionError on the configsvr which should force the moveChunk to fail - if the configsvr is the donor that had a failover, the new primary will not have this failpoint set, and the command will succeed.