Details

    • Type: Bug
    • Status: Resolved
    • Priority: High
    • Resolution: Duplicate
    • Affects Version/s: Marathon 1.4.2
    • Fix Version/s: None
    • Component/s: API
    • Labels:

      Description

      This is in our Prod Cluster with DC/OS EE 1.9 and Marathon 1.4.2.

       

      Expected behavior:

      When changing a Service ID of a running service I would expect it to run a new service with the new name.

       

      Seen behavior:

      No changes made.  Also no error messages or anything that would lead to the conclusion that a change of the Service ID won't turn into effect.

       

      Video of the bug: https://cl.ly/1z362s0S3p0A

       

      Workaround:

      Manually destroying the app and re-adding it under new Service ID.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                fabian Fabian Baier
                Team:
                Orchestration Team
                Watchers:
                Fabian Baier, Ivan Chernetsky, Johannes Unterstein, Jörg Schad (Inactive), Marco Monaco, Matthias Eichstedt
              • Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: