SERVER-42610 Flip order of assert.lte arguments in shards_and_config_return_last_committed_optime.js

(cherry picked from commit d101a617bada9252a4f0a29b8f615ee62abb979b)

1 files changed, 2 insertions, 2 deletions

diff --git a/jstests/sharding/shards_and_config_return_last_committed_optime.js b/jstests/sharding/shards_and_config_return_last_committed_optime.js
index efe6d7f431b..780090d9f67 100644
--- a/jstests/sharding/shards_and_config_return_last_committed_optime.js
+++ b/jstests/sharding/shards_and_config_return_last_committed_optime.js
@@ -55,8 +55,8 @@ function assertCmdReturnsLastCommittedOpTime(testDB, cmdObj, connType, expectSuc
         // lastCommittedOpTime will be greater than the lastCommittedOpTime timestamp in its
         // body. Assert the timestamp is <= lastCommittedOpTime to account for this.
         const statusRes = assert.commandWorked(testDB.adminCommand({replSetGetStatus: 1}));
-        assert.lte(0,
-                   bsonWoCompare(res.lastCommittedOpTime, statusRes.optimes.lastCommittedOpTime.ts),
+        assert.lte(bsonWoCompare(res.lastCommittedOpTime, statusRes.optimes.lastCommittedOpTime.ts),
+                   0,
                    "lastCommittedOpTime in command response, " + res.lastCommittedOpTime +
                        ", is not <= to the replSetGetStatus lastCommittedOpTime timestamp, " +
                        statusRes.optimes.lastCommittedOpTime.ts + ", cmd was: " + tojson(cmdObj));