When delete_range_deletion_tasks_on_stepup_after_drop_collection.js is run with a catalog shard, the fail points it sets to pause metadata refreshes prevents the migration it runs from completing after stepup. This doesn't necessarily seem wrong, but doesn't happen with a dedicated config server, so we should further investigate and decide if this is ok.