The migration_fails_if_exists_in_rangedeletions.js test causes a chunk migration to block forever due to the presence of an overlapping range to clean up and the range deleter being paused using a failpoint on the recipient shard. Disabling the suspendRangeDeletion failpoint allows the chunk migration to proceed. If the ongoing chunk migration doesn't complete quickly enough, then the drop command to clean up the sharded collection before running the next test scenario will fail with a LockBusy error response.

Re-running the moveChunk command which had its maxTimeMS expire after the suspendRangeDeletion failpoint was disabled would ensure the chunk migration is no longer in progress before the drop command is run.