SERVER-45919 replSetReconfig should be allowed to fail with InterruptedDueToReplStateChange in reconfig_during_election.js

(cherry picked from commit f44afc0ce5c5a0a8e7dacd2b0d3a042fc989a21d)

1 files changed, 7 insertions, 2 deletions

diff --git a/jstests/replsets/reconfig_during_election.js b/jstests/replsets/reconfig_during_election.js
index b73303bd60d..3c36ef58adc 100644
--- a/jstests/replsets/reconfig_during_election.js
+++ b/jstests/replsets/reconfig_during_election.js
@@ -1,5 +1,6 @@
 /**
- * SERVER-37255: replSetReconfig runs on a node that is concurrently processing an election win.
+ * SERVER-37255: replSetReconfig runs on a node that is concurrently processing an election win and
+ * does not result in an invariant.
  */
 
 (function() {
@@ -42,7 +43,11 @@ jsTestLog("Try to interrupt it with a reconfig");
 
 config.members[nodes.indexOf(candidate)].priority = 2;
 config.version++;
-assert.commandWorked(candidate.adminCommand({replSetReconfig: config, force: true}));
+// While the candidate is stepping up, it it possible for the RstlKillOpThread to kill this reconfig
+// command before it succeeds. Failing with an InterruptedDueToReplStateChange error is acceptable
+// here because we are testing that the reconfig command does not cause the server to invariant.
+assert.commandWorkedOrFailedWithCode(candidate.adminCommand({replSetReconfig: config, force: true}),
+                                     ErrorCodes.InterruptedDueToReplStateChange);
 
 assert.commandWorked(candidate.adminCommand(
     {configureFailPoint: "electionHangsBeforeUpdateMemberState", mode: "off"}));