Details

    • Sprint:
      Marathon 2018-29, Marathon 2018-30
    • Story Points:
      1
    • Build artifact:
      Marathon-v1.7.174
    • Parent Initiative:
      D2IQ-47610 - [Orchestration] Chores

      Description

      When creating an application with a persistent volume using `POST /v2/apps`, the API will automatically create the required unreachableStrategy:
          "unreachableStrategy": "disabled",

      However, when creating the same application using `PUT /v2/apps/:appId`, an Object is not valid/422 error is returned with the following detail:
      unreachableStrategy must be disabled for resident tasks

      The REST API documentation states that POST and PUT are equivalent.

      The workaround is either to forgo PUT for POST or to explicitly specify the required unreachableStrategy in the PUT payload.

      Example payload is attached.

      Acceptance criteria

      Given an empty instance of Marathon
      When I PUT the attached payload to /v2/apps
      Then the application should be created successfully
      And the unreachableStrategy should be set to "disabled"

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                alenavarkockova Alena Varkockova
                Reporter:
                cgbaker Chris Baker
                Team:
                ( DO NOT USE ) Orchestration Team
                Watchers:
                Chris Baker, Mergebot, Tim Harper
              • Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: