Resharding forces a catalog cache refresh, which sometimes forces a no-op write. This write uses a write concern timeout of 60 seconds - currently we don't retry on WriteConcernTimeout, nor do currently consider this a transient error, and so if there's slowness or some network issue that causes this write to fail, we'll fail the entire resharding operation with an fassert.