Uploaded image for project: 'DC/OS'
  1. DCOS-255

Marathon should have some mechanism to allow graceful upgrades when new validation is added

    Details

    • Type: Improvement
    • Status: Open (View workflow)
    • Priority: Medium
    • Resolution: Unresolved
    • Affects versions: None
    • Fix versions: None
    • Components: marathon
    • Labels:
      None
    • Sprint:

      Description

      With DC/OS 1.7 -> 1.8, marathon added a new validation that no two apps share the same servicePorts.

      This makes it so that when you upgrade from 1.7 to 1.8, some apps which used to deploy, don't deploy any more (and their marathon.json can't be edited until the servicePort conflict is eliminated).

      It would be really nice if Marathon had some sort of a mechanism for looking at existing apps, marking problems / issues with them that new validation finds, and displaying those as warnings to the user while not blocking pre-existing apps from being editable / deployable. New apps should ideally be required to follow all the validation.

        Attachments

          Activity

            People

            • Assignee:
              marcomonaco Marco Monaco
              Reporter:
              cmaloney Cody Maloney
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: