CheckMetadataConsistency hook relies on the isMaster command to asses if the fixture cluster is sharded.
In the integration_tests_sharded suite we run at least two tests (1, 2) that set a failPoint to make the isMaster command to unconditionally fail, thus if the CheckMetadataConsistency hook runs while the fail point is set it will fail.
I can think of two possible solution here:
- Do not run the CheckMetadataConsistency hook in the intergration_tests_sharded suite
- Keep enable the hook on that suite but skip the speicifc tests that make the isMaster command to fail. We already did it in the past using this approach.