-
Type: Bug
-
Resolution: Fixed
-
Priority: Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
ALL
-
Sharding 2020-04-20, Sharding 2020-05-04, Sharding 2020-05-18
-
24
Tests: applyOps_c_renameCollection_twoDbs and renameCollection_twoDbs both make use of the `movePrimary` command which is available on mongos only, but do not specify `skipUnlessSharded`. It's unclear which resolution is prefered.
- Ignore CommandUnknown error. This is the current state, if desired we should explicitly comment that failure is an option.
- Specify `skipUnlessSharded: true` if this is in deed a mongos only test.
- related to
-
SERVER-48620 Run movePrimary in renameCollection_twoDBs in commands roles tests when on sharded systems
- Closed