[SERVER-71914] Exclude FLE2 FSM tests from concurrency multi_stmt_txn suites Created: 06/Dec/22  Updated: 29/Oct/23  Resolved: 07/Dec/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0-rc0

Type: Task Priority: Major - P3
Reporter: Erwin Pe Assignee: Erwin Pe
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Security 2022-12-12
Participants:
Linked BF Score: 0

 Description   

The FLE2 FSM tests (fle2_compact.js and fle2_crud.js) run operations that do not use the same DB (and session) as the one passed in on every state function call by the FSM runner, instead the encrypted operations in each state function operate within the context of an EncryptedClient object, which has its own Mongo and DB object.  Meanwhile, the multi_stmt_txn suites assume that every operation running within a state function will be part of a single transaction, and so it enables a retry mechanism in the FSM runner to retry the transaction in cases of transient errors. Because the auto-retry may cause the state function to be run multiple times, and because each state function in a FLE 2 test runs commands that are not a part of a transaction, it is possible for FLE 2 operations to execute more times than expected, and thus lead to assertion failures during teardown.



 Comments   
Comment by Githook User [ 07/Dec/22 ]

Author:

{'name': 'Erwin Pe', 'email': 'erwin.pe@mongodb.com', 'username': 'erwee'}

Message: SERVER-71914 Exclude FLE2 FSM tests from concurrency multi_stmt_txn suites
Branch: master
https://github.com/mongodb/mongo/commit/de5f18831059bb83d57ea1e58d539359796ba090

Generated at Thu Feb 08 06:20:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.