SERVER-55382 Move NoSuchTransaction error to skippableErrors

(cherry picked from commit 801a0f84afb7f22c91f93e1a67463181a8e032b9)

1 files changed, 3 insertions, 3 deletions

diff --git a/jstests/concurrency/fsm_workloads/random_moveChunk_update_shard_key.js b/jstests/concurrency/fsm_workloads/random_moveChunk_update_shard_key.js
index 1fe17a29ac8..a70b9e70c6d 100644
--- a/jstests/concurrency/fsm_workloads/random_moveChunk_update_shard_key.js
+++ b/jstests/concurrency/fsm_workloads/random_moveChunk_update_shard_key.js
@@ -83,15 +83,15 @@ var $config = extendWorkload($config, function($config, $super) {
             ErrorCodes.WriteConflict,
             ErrorCodes.LockTimeout,
             ErrorCodes.PreparedTransactionInProgress,
-            ErrorCodes.ShardInvalidatedForTargeting
+            ErrorCodes.ShardInvalidatedForTargeting,
+            ErrorCodes.NoSuchTransaction
         ];
 
         // If we're running in a stepdown suite, then attempting to update the shard key may
         // interact with stepdowns and transactions to cause the following errors. We only expect
         // these errors in stepdown suites and not in other suites, so we surface them to the test
         // runner in other scenarios.
-        const stepdownErrors =
-            [ErrorCodes.NoSuchTransaction, ErrorCodes.ConflictingOperationInProgress];
+        const stepdownErrors = [ErrorCodes.ConflictingOperationInProgress];
 
         if (this.runningWithStepdowns) {
             skippableErrors.push(...stepdownErrors);