It's possible that when running analyzeShardKey in a suite with config transitions that the collection being analyzed is dropped out from under analyzeShardKey if its db primary was the config shard. This will result in a NamespaceNotFound error to be thrown here and fail the test.

Consider adding NamespaceNotFound to the list of acceptable errors if running in a config transition suite.