[SERVER-76306] Exclude command_let_variables.js from sharded_retryable_writes_downgrade Created: 19/Apr/23  Updated: 29/Oct/23  Resolved: 20/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0, 7.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: David Storch Assignee: David Storch
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0
Sprint: QE 2023-05-01
Participants:
Linked BF Score: 66

 Description   

The modifications to command_let_variables.js from related ticket SERVER-75356 added some test cases which run explain. But explain against a sharded cluster doesn't currently accept readConcern, so the test fails in the sharded_retryable_writes_downgrade passthrough with an error like this:

            uncaught exception: Error: command failed: {
            	"ok" : 0,
            	"errmsg" : "Command explain does not support { readConcern: { level: \"majority\", afterClusterTime: Timestamp(1681916234, 13), provenance: \"clientSupplied\" } } :: caused by :: read concern not supported",
            	"code" : 72,
            	"codeName" : "InvalidOptions",



 Comments   
Comment by Githook User [ 20/Apr/23 ]

Author:

{'name': 'David Storch', 'email': 'david.storch@mongodb.com', 'username': 'dstorch'}

Message: SERVER-76306 Exclude command_let_variables.js from sharded_retryable_writes_downgrade

(cherry picked from commit 041756701e6202ff3054106bf9ae9b966e55dbb2)
Branch: v7.0
https://github.com/mongodb/mongo/commit/1ecea159b5fcf2f944d3b2824e3b33784ae44505

Comment by Githook User [ 20/Apr/23 ]

Author:

{'name': 'David Storch', 'email': 'david.storch@mongodb.com', 'username': 'dstorch'}

Message: SERVER-76306 Exclude command_let_variables.js from sharded_retryable_writes_downgrade
Branch: master
https://github.com/mongodb/mongo/commit/041756701e6202ff3054106bf9ae9b966e55dbb2

Comment by David Storch [ 19/Apr/23 ]

Requesting backport to v7.0, since it looks like the failure is happening in that branch as well.

Generated at Thu Feb 08 06:32:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.