-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2026-11-09
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The allows replSetStepDown and replSetStepUp case in direct_shard_connection_auth_rs_commands.js assumes that promoting a secondary leaves the former primary running and able to become secondary. In DSC, unconditional step-down shuts down the former primary rather than transitioning it in-process (tracked by SERVER-124385). Consequently, the test's subsequent topology waits and cleanup cannot assume all members remain available. In addition, replSetMaintenance and replSetAbortPrimaryCatchUp commands are not supported in DSC.
As part of this ticket, we should 1) Exclude those three test cases, and 2) Add the direct_shard_connection_auth_rs_commands.js test to no_passthrough_disagg_override_replsets.
- related to
-
SERVER-138700 Investigate noPassthrough sharding coverage for tests applying replication lag injection
-
- Closed
-