DRIVERS-3556 skip affected CSOT change stream tests on 9.0+ sharded (#1962)

Author: kevinAlbs

source/client-side-operations-timeout/etc/templates/retryability-timeoutMS.yml.template

@@ -91,7 +91,16 @@ tests:
           isTimeoutError: true
   - description: "operation is retried multiple times for non-zero timeoutMS - {{operation.operation_name}} on {{operation.object}}"
     runOnRequirements:
+    {%- if operation.operation_name == 'createChangeStream' %}
       - minServerVersion: "4.3.1" # failCommand errorLabels option
+        topologies: ["replicaset"]
+      - minServerVersion: "4.3.1" # failCommand errorLabels option
+        maxServerVersion: "8.99" # Skip sharded 9.0+ due to reasons noted in DRIVERS-3556.
+        # Removing the skip may be desired in the future if this test migrates from timeoutMS to maxTimeMS. See DRIVERS-3556 for a suggested approach: add a unified test runner option to advance the config server's cluster time immediately before opening a change stream. Otherwise, existing tests using maxTimeMS < periodicNoopIntervalSecs on 9.0+ sharded clusters may unexpectedly fail with server timeouts.
+        topologies: ["sharded"]
+    {%- else %}
+      - minServerVersion: "4.3.1" # failCommand errorLabels option
+    {%- endif %}
     operations:
       - name: failPoint
         object: testRunner

source/client-side-operations-timeout/tests/override-operation-timeoutMS.json

@@ -160,6 +160,13 @@ tests:
                 listDatabases: 1
                 maxTimeMS: { $$exists: false }
   - description: "timeoutMS can be configured for an operation - createChangeStream on client"
+    runOnRequirements:
+    - minServerVersion: "4.4"
+      topologies: ["replicaset"]
+    - minServerVersion: "4.4"
+      maxServerVersion: "8.99" # Skip sharded 9.0+ due to reasons noted in DRIVERS-3556.
+      # Removing the skip may be desired in the future if this test migrates from timeoutMS to maxTimeMS. See DRIVERS-3556 for a suggested approach: add a unified test runner option to advance the config server's cluster time immediately before opening a change stream. Otherwise, existing tests using maxTimeMS < periodicNoopIntervalSecs on 9.0+ sharded clusters may unexpectedly fail with server timeouts.
+      topologies: ["sharded"]
     operations:
       - name: failPoint
         object: testRunner
@@ -452,6 +459,13 @@ tests:
                 ping: 1
                 maxTimeMS: { $$exists: false }
   - description: "timeoutMS can be configured for an operation - createChangeStream on database"
+    runOnRequirements:
+    - minServerVersion: "4.4"
+      topologies: ["replicaset"]
+    - minServerVersion: "4.4"
+      maxServerVersion: "8.99" # Skip sharded 9.0+ due to reasons noted in DRIVERS-3556.
+      # Removing the skip may be desired in the future if this test migrates from timeoutMS to maxTimeMS. See DRIVERS-3556 for a suggested approach: add a unified test runner option to advance the config server's cluster time immediately before opening a change stream. Otherwise, existing tests using maxTimeMS < periodicNoopIntervalSecs on 9.0+ sharded clusters may unexpectedly fail with server timeouts.
+      topologies: ["sharded"]
     operations:
       - name: failPoint
         object: testRunner
@@ -1028,6 +1042,13 @@ tests:
                 listIndexes: *collectionName
                 maxTimeMS: { $$exists: false }
   - description: "timeoutMS can be configured for an operation - createChangeStream on collection"
+    runOnRequirements:
+    - minServerVersion: "4.4"
+      topologies: ["replicaset"]
+    - minServerVersion: "4.4"
+      maxServerVersion: "8.99" # Skip sharded 9.0+ due to reasons noted in DRIVERS-3556.
+      # Removing the skip may be desired in the future if this test migrates from timeoutMS to maxTimeMS. See DRIVERS-3556 for a suggested approach: add a unified test runner option to advance the config server's cluster time immediately before opening a change stream. Otherwise, existing tests using maxTimeMS < periodicNoopIntervalSecs on 9.0+ sharded clusters may unexpectedly fail with server timeouts.
+      topologies: ["sharded"]
     operations:
       - name: failPoint
         object: testRunner

source/client-side-operations-timeout/tests/override-operation-timeoutMS.yml

@@ -1315,6 +1315,11 @@ tests:
   - description: "operation is retried multiple times for non-zero timeoutMS - createChangeStream on client"
     runOnRequirements:
       - minServerVersion: "4.3.1" # failCommand errorLabels option
+        topologies: ["replicaset"]
+      - minServerVersion: "4.3.1" # failCommand errorLabels option
+        maxServerVersion: "8.99" # Skip sharded 9.0+ due to reasons noted in DRIVERS-3556.
+        # Removing the skip may be desired in the future if this test migrates from timeoutMS to maxTimeMS. See DRIVERS-3556 for a suggested approach: add a unified test runner option to advance the config server's cluster time immediately before opening a change stream. Otherwise, existing tests using maxTimeMS < periodicNoopIntervalSecs on 9.0+ sharded clusters may unexpectedly fail with server timeouts.
+        topologies: ["sharded"]
     operations:
       - name: failPoint
         object: testRunner
@@ -1755,6 +1760,11 @@ tests:
   - description: "operation is retried multiple times for non-zero timeoutMS - createChangeStream on database"
     runOnRequirements:
       - minServerVersion: "4.3.1" # failCommand errorLabels option
+        topologies: ["replicaset"]
+      - minServerVersion: "4.3.1" # failCommand errorLabels option
+        maxServerVersion: "8.99" # Skip sharded 9.0+ due to reasons noted in DRIVERS-3556.
+        # Removing the skip may be desired in the future if this test migrates from timeoutMS to maxTimeMS. See DRIVERS-3556 for a suggested approach: add a unified test runner option to advance the config server's cluster time immediately before opening a change stream. Otherwise, existing tests using maxTimeMS < periodicNoopIntervalSecs on 9.0+ sharded clusters may unexpectedly fail with server timeouts.
+        topologies: ["sharded"]
     operations:
       - name: failPoint
         object: testRunner
@@ -2740,6 +2750,11 @@ tests:
   - description: "operation is retried multiple times for non-zero timeoutMS - createChangeStream on collection"
     runOnRequirements:
       - minServerVersion: "4.3.1" # failCommand errorLabels option
+        topologies: ["replicaset"]
+      - minServerVersion: "4.3.1" # failCommand errorLabels option
+        maxServerVersion: "8.99" # Skip sharded 9.0+ due to reasons noted in DRIVERS-3556.
+        # Removing the skip may be desired in the future if this test migrates from timeoutMS to maxTimeMS. See DRIVERS-3556 for a suggested approach: add a unified test runner option to advance the config server's cluster time immediately before opening a change stream. Otherwise, existing tests using maxTimeMS < periodicNoopIntervalSecs on 9.0+ sharded clusters may unexpectedly fail with server timeouts.
+        topologies: ["sharded"]
     operations:
       - name: failPoint
         object: testRunner