-
Type: Task
-
Resolution: Fixed
-
Priority: Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
None
For some reason this test fails against a sharded MongoDB 3.7 deployment. It seems mongos ignores the impossible write concern. This could also be a bug in the server.
[2018/02/12 17:07:40.890] ====================================================================== [2018/02/12 17:07:40.890] FAIL [0.031s]: test_create (test_collection.TestCollection) [2018/02/12 17:07:40.890] ---------------------------------------------------------------------- [2018/02/12 17:07:40.890] Traceback (most recent call last): [2018/02/12 17:07:40.890] File "/data/mci/ed576f18200cc91000337e52fdf4b32f/src/test/__init__.py", line 365, in wrap [2018/02/12 17:07:40.890] return f(*args, **kwargs) [2018/02/12 17:07:40.890] File "/data/mci/ed576f18200cc91000337e52fdf4b32f/src/test/test_collection.py", line 155, in test_create [2018/02/12 17:07:40.890] create=True) [2018/02/12 17:07:40.890] AssertionError: OperationFailure not raised
- depends on
-
SERVER-33317 3.7 sharded clusters ignore create command write concern
- Closed