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

FSM tests should reset the FCV to the fixture default value

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 5.0.9, 6.0.0-rc7
    • Component/s: None
    • ALL
    • Sharding EMEA 2022-06-27, Sharding EMEA 2022-07-11, Sharding EMEA 2022-07-25, Sharding EMEA 2022-08-08, Sharding EMEA 2022-08-22, Sharding EMEA 2022-09-05

      Some of our FSM tests modify the FCV but they don't reset it during the teardown. This means that any subsequent test that will be executed afterwards using the same cluster will run with an unexpected FCV.

      A non-exaustive list of FSM tests that change the FCV:

      • jstests/concurrency/fsm_workloads/autosplit_setFCV_downgrade_from_60.js
      • jstests/concurrency/fsm_workloads/random_DDL_setFCV_operations.js
      • jstests/concurrency/fsm_workloads/drop_database_sharded_setFCV.js
      • jstests/concurrency/fsm_workloads/random_internal_transactions_setFCV_operations.js
      • jstests/concurrency/fsm_workloads/random_DDL_CRUD_setFCV_operations.js

            Assignee:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: