Initially, this ticket tracked the work to make the assertion about the presence of the 'errInfo' field in 'doc_validation.js' only when we know that the mongods in a sharded cluster accepting writes are upgraded to 4.6 as this would give us the multiversion test coverage desired where we verify that the errInfo field is propagated from a 4.6 shard primary to a 4.4 mongos correctly. However, when the two named tests are run in the 'sharding_jscore_multiversion_passthrough' suite, the 2 shards are always in a mixed version configuration (that is, one shard always has a 4.6 primary and the other is always a 4.4 primary). As such, neither test can be configured in such a way to achieve the desired coverage and therefore, the tests should be blacklisted from the multiversion suites and a followup ticket should be filed to write a targeted test that achieves the desired coverage.