We implicitly create a collection (and its _id index) while trying to create an invalid index. We expect the collection creation and _id index creation to succeed, but not the other index creation. This can cause issues in passthrough suites that use network_error_and_txn_override.js because we attach write concern majority to all writes. If the write concern fails, we don't retry the command because the command also fails with the expected error that the index couldn't be created. As a result, if the test steps up a node that did not receive the command to create the index, it will not have created the collection, so this check for the number of indexes on the collection fails.