The handler of the test-only _shardsvrCheckMetadataConsistencySecondaryParticipant command requires the ShardingState to be initialized to produce its response.

Such a condition can only be satisfied when the shard identity document gets read and installed (a step that may occur during different phases of the mongod startup sequence, depending on multiple factors).

To ensure that _shardsvrCheckMetadataConsistencySecondaryParticipant never fails with a ShardingStateNotInitialized error, the command handler should explicitly invoke ShardingState::awaitClusterRoleRecovery().