As part of the BF-44827 we concluded that there are still few occasions where setFCV upgrade from 8.0 to 9.0 is misbehaving when interleaved with metadata consistency checks resulting in reporting inconsistencies that occur just due to upgrade being ran in parallel (e.g. false-positive). Ideally this interleaving should be prevented by recently introduced OptimisticFCVFeatureFlagGuard. However the check that was fired in this BF (e.g. "Chunk entries not found in the durable shard catalog") is not adding the inconsistencies to the authShardsInconsistencies (we're passing inconsistencies vector into the call, not authShardInconsistencies vector) and therefore the reported inconsistencies are not getting discarded once the lambda executed at the exit call of the function detects the change in FCV. The fix should be simple enough to change the variable we're passing here.