lagged_config_secondary.js should not rely on last-lts version

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Sharding EMEA 2021-08-09
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      lagged_config_secondary.js test is relying on the last-lts version to choose the old or the new name of disableShardingUptimeReporting failpoint

      This logic is wrong because the last-lts version change on every release, we should make this logic rely on a fixed binary version (in this case 4.4)

      The goal of this ticket is to fix the test and remove the disabled_due_to_server_58295 tag.

              Assignee:
              Allison Easton
              Reporter:
              Tommaso Tocci
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: