No longer accept FailPointSetFailed errors on jstests that use migrationRecipientFailPostCommitRefresh failpoint

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding EMEA 2022-07-11
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-58991 introduces a new failpoint migrationRecipientFailPostCommitRefresh with semantics analogous to doNotRefreshRecipientAfterCommit. Because this new failpoint does not exist in 5.0 binaries, tests that are run on multiversion suites need to account for it's possible non-existence.

      This ticket is to remove this relaxation after 6.0 has been released. At this point, multiversion tests will always run on binaries that support the new failpoint.

            Assignee:
            Enrico Golfieri
            Reporter:
            Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: