As a part of the preSetup we run the precmdShardKey function which runs a chunk split. The split can trigger a metadata refresh that has a majority write concern. That write concern will fail since previously in the testing code we have taken down one of the secondaries.

To resolve this we need to make the test resilient to write concern failures in the preSetup. Either we ignore the errors and skip the test, or figure out some other workaround.

Part of the issue with the current set up is that as part of the testing infrastructure here we stop secondaries before any test is ran. Later when running the test we run a provided preSetup function, in this case precmdShardKey.

If any preSetup function passed in requires write concern majority for any potential commands it runs, the test will fail. It seems a larger refactoring may be necessary to ensure that anything run in preSetup does not require write concern majority, or it should ensure that all secondaries are up and running when executing preSetup.