Two catalog shard tests fail the checkShardFilteringMetadata hook at ShardingTest shutdown. Both fail because a secondary does not have filtering metadata in its shardingState response, and both involve either adding a shard or reconfiguring a node into a shard near the end of the test, so this may be the expected behavior, but we should verify this.

jstests/sharding/reconfig_fails_no_cwwc_set_sharding.js

jstests/sharding/implicit_default_write_concern_add_shard.js