The reason why this was added in multiVersion tests is that awaitLastOpCommitted relies on certain fields to exist in replSetGetStatus command that doesn't exist in v3.2 mongod. After v3.4, multiVersion tests will now use v3.4 mongods as the old mongods, so this issue goes away.
- is related to
-
SERVER-24087 Make sure config servers are caught up after ShardingTest starts up
-
- Closed
-