Config upgrade v3 to v4 fails when old upgrade collections doesn't exist on the server

ExportXMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.4.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If a previous upgrade failed, it's possible that the previous upgrade collections are missing. We try to clean these up as part of the upgrade process, but failing to clean the collections up shouldn't abort the upgrade.

            Assignee:
            Unassigned
            Reporter:
            Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: