stopping the container causes the client not to remove /evergreen/booting.txt

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • Component/s: evergreen
    • None
    • Evergreen - Milestone 1

      To reproduce:

      • Start the container and let it download and upgrade everything
      • Stop the container
      • Start the container
      • Navigate to the web UI and be trapped on the booting screen forever.

      Seen in my demo instance, the client didn't automatically remove booting.txt leaving the user to think that the instance was stuck

            Assignee:
            R. Tyler Croy
            Reporter:
            R. Tyler Croy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: