Uploaded image for project: 'HAL'
  1. HAL
  2. HAL-1548

Replace deployment in admin console ignores runtime-name

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • 3.0.8.Final
    • None
    • None
    • None
    • Hide

      How reproducible:
      Always.

      Steps to Reproduce:
      1. Go to "Manage Deployments" screen in the admin console
      2. Choose deployments and click "Add" button
      3. Upload deployment (abc-SNAPSHOT.war) and change runtime name (abc.war)
      4. Go to "Manage Deployments" screen in the admin console
      5. Choose deployments and click "Replace" button on the further installed deployment
      6. After re-deployment runtime name has changed to (abc-SNAPSHOT.war)

      Show
      How reproducible: Always. Steps to Reproduce: 1. Go to "Manage Deployments" screen in the admin console 2. Choose deployments and click "Add" button 3. Upload deployment (abc-SNAPSHOT.war) and change runtime name (abc.war) 4. Go to "Manage Deployments" screen in the admin console 5. Choose deployments and click "Replace" button on the further installed deployment 6. After re-deployment runtime name has changed to (abc-SNAPSHOT.war)
    • Workaround Exists
    • Hide

      Remove deployment
      Add deployment with correct runtime name.

      Show
      Remove deployment Add deployment with correct runtime name.

      When using the "Add" deployment feature in the admin console, change the runtime name.

      When using the "Replace" deployment feature in the admin console, the entered runtime name is ignored and the deployment name is used

      Actual results:
      The runtime name is set to the same value as deployment name, not the entered runtime name.

      Expected results:
      The runtime name should not be touched and keep its old runtime name.

              cmiranda@redhat.com Claudio Miranda
              mhofmann_jira Markus Hofmann (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: