Details
Description
CRUD_and_commands_with_createindexes.js concurrently runs createIndexes and dropCollection on the same namespace, which can lead to ConflictingOperationInProgress errors if the createIndexes triggers a shard version refresh that finds chunks no longer exist for the collection because of a concurrent drop.
Currently this test handles that error by appending a TransientTransactionError error label to the response in suites that set TestData.runInsideTransaction to true, which triggers an automatic retry if the command is running in a transaction. The command may not be in a transaction even if that flag is set, and in this case, the error label will still be attached but there will be no retry, and the test will fail.
Instead, ConflictingOperationInProgress should either be retried on or ignored, since it is an expected error under these conditions.