Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-93116

api_version_test_expression.js must be skipped in case of fcv upgrade/downgrade

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc17
    • Affects Version/s: 8.0.0-rc0, 8.1.0-rc0
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0
    • CAR Team 2024-08-05
    • 0

      Context

      In case a {create ... } passes from the createCollectionCoordinator to track a collection, the api check is not performed. This will be fixed in SERVER-92954. Until then, SERVER-92953 introduced a check to skip test cases where the API version is explicitly checked and feature flag "trackUnshardedCollectionUponCreation" is enabled.  (which redirects {create .. } to the createCollectionCoordinator)

      Issue

      In case the feature flag is disabled, we should skip the test case. However, the suite fcv_upgrade_downgrade_sharding_jscore_passthrough can still randomly enable the feature flag right after the check, but before executing the {create .. } command. That would redirect the create to the createCollectionCoordinator, causing the test to fail. 
      This is a known problem, which is usually fixed by disabling the test in case of fcv upgrade/downgrade suites.

       

      note: The test here only checks on the function signature, but forgets to call it. We can fix that on this ticket.

            Assignee:
            pol.pinol@mongodb.com Pol Pinol
            Reporter:
            enrico.golfieri@mongodb.com Enrico Golfieri
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: