This check was added when the last-lts version was v4.4 and invalid write concerns passed to renameCollection were expected to trigger a write concern error.
Starting from v5.0, no write concerns is propagated anymore for renameCollection as the majority write concern is applied by default.
- split from
-
SERVER-58351 Fix disabled Sharding tests failing in multiversion suites due to changing latest release to 5.1
- Closed