tenant_migration_conflicting_donor_start_migration_cmds.js should not automatically forget migrations

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Server Serverless 2022-03-21
    • 40
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This first test runs two migrations and expects the second to join the first, but each migration is forgotten as soon as it completes. So, it's possible that the first migration's state doc has already been deleted by the time the second is run. If this happens, we'll fail any assertions that are made around the second migration joining the first. The test should instead wait to forget the migrations until after both have run.

            Assignee:
            Janna Golden (Inactive)
            Reporter:
            Janna Golden (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: