If a database is dropped and recreated and then configure collection balancing is run immediately, the call to getShardedCollectionRoutingInfo can return a stale uuid for the collection which will cause a uassertion that there is a conflicting operation in progress. The command will retry, but will still get stale information. We should update the call to the catalog cache to use getShardedCollectionRoutingInfoWithRefresh