-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
-
2
The checkMetadataConsistency hook runs on a separate shell which does not authenticate.
In case a test enables authentication. The checkMetadataConsistency will error with Error.Unauthorized.
Before SERVER-70396 this behaviour was hidden behind the feature flag check which used to fail with "Unauthorized". However the try-catch would swallow the error causing the check to be skipped for the wrong reason.
After SERVER-70396 we will set Error.Unauthorized as TransientError
At the current state, the checkMetadataConsistency is always skipped in case authentication is enabled, causing a reduced test coverage.
This ticket is to make checkMetadataConsistency authenticate before running in case of enabled authentication. Similar to what is done in check_shard_filtering_metadata
- depends on
-
SERVER-70396 Remove Feature Flag for PM-3020
-
- Closed
-
- is duplicated by
-
SERVER-89278 MetadataConsistencyChecker and checkUUIDsConsistentAcrossCluster silently fail with auth
-
- Closed
-