There have been several issues in multiversion tests where a cluster is upgraded, and a subsequent query/operation fails with "not master" because the upgrade isn't fully complete or the shards aren't in sync with each other. Notably SERVER-46124 and SERVER-47159 have workarounds in a single test but we should develop a more generic solution going forward.
- related to
-
SERVER-46124 Add wait for shards to see the latest state of other replica set in 'compound_hashed_shard_key.js' test
- Closed
-
SERVER-47159 Wait for cluster to stabilize after shard upgrade in 'agg_with_comment_during_upgrade.js' test
- Closed