The test agg_lookup.js captures any exception thrown by an aggregation command to avoid failing when the command fails with expected errors caused by chunk or collection movements, like QueryPlanKilled.

However, if the suite has been configured to work with multi-statement transactions, all the errors thrown by the test state are captured by the auto_retry_transactions.js machinery, so the entire state gets retried for specific errors.

The problem is that when agg_lookup.js fails with ShardNot found, instead of throwing the original ShardNot error, the test is failing with an assert exception because of this check.