SERVER-53785 Test WriteConcernErrors are preserved with the mongos implementation of drop command

1 files changed, 20 insertions, 0 deletions

diff --git a/jstests/sharding/write_concern_basic.js b/jstests/sharding/write_concern_basic.js
new file mode 100644
index 00000000000..ae27edad6cd
--- /dev/null
+++ b/jstests/sharding/write_concern_basic.js
@@ -0,0 +1,20 @@
+// Test that certain basic commands preserve write concern errors.
+// @tags: [ requires_fcv_49, ]
+//
+
+(function() {
+"use strict";
+
+load("jstests/sharding/libs/failpoint_helpers.js");
+
+let st = new ShardingTest({shards: 1, config: 1});
+
+{
+    let db = st.s.getDB("test");
+    failCommandsWithWriteConcernError(st.rs0, ["drop", "_shardsvrDropCollectionParticipant"]);
+    assert.commandWorked(db.collection.insert({"a": 1}));
+    assert.commandFailedWithCode(db.runCommand({drop: "collection"}), 12345);
+}
+
+st.stop();
+})();
\ No newline at end of file