-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2025-06-09
-
None
-
3
-
TBD
-
🟩 Routing and Topology
-
None
-
None
-
None
-
None
-
None
-
None
-
0
If the antithesis docker image build runs the jstestfuzz_sharded_with_config_transitions_and_add_remove_shard then in some weird cases an addShard from the test happens after the hook restarted the shard but before it adds it back.
As a temporary solution we remove the add_remove_shard part from the antithesis, but we should figure out, if it's possible to prevent jsfuzz test to do add shard within specific suites
- is related to
-
SERVER-105954 Exclude topology changes in fuzztests if hook does it already
-
- Closed
-
-
SERVER-105955 Revert SERVER-105199
-
- Closed
-