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

Replacing a deployment (which uses a different runtime name), starts using the filename as runtime-name

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • None
    • Deployment Management
    • None
    • Hide
      1. Setup
        Open the web console, go to Deployents -> Content Repository -> Add
        -> Upload new deployment
        -> Choose File (testEar.ear for me) -> Next
        -> Change runtime name to otherName.ear -> Finish

      Assign the deployment to a Server Group

      1. Verify the runtime name is ok
        Go to Server Groups -> (your server group) -> testEar.ear
        Verify that the runtime name is `otherName.ear`
      1. Replace and Break
        Go to the Content Repository, select testEar.ear and 'Replace'.

      You can choose the same 'testEar.ear' file then 'Finish'

      1. Verify it's wrong
        Go to Server Groups -> (your server group) -> testEar.ear
        Verify that the runtime name is now `testEar.ear`
      Show
      Setup Open the web console, go to Deployents -> Content Repository -> Add -> Upload new deployment -> Choose File (testEar.ear for me) -> Next -> Change runtime name to otherName.ear -> Finish Assign the deployment to a Server Group Verify the runtime name is ok Go to Server Groups -> (your server group) -> testEar.ear Verify that the runtime name is `otherName.ear` Replace and Break Go to the Content Repository, select testEar.ear and 'Replace'. You can choose the same 'testEar.ear' file then 'Finish' Verify it's wrong Go to Server Groups -> (your server group) -> testEar.ear Verify that the runtime name is now `testEar.ear`

      This is a two step problem. If an ear has been uploaded and configured to use a different runtime name that works and the domain uses the correct runtime name.

      If I replace the ear it doesn't have an input box to choose a new runtime name- yet it defaults the new runtime name to the filename that's being used to replace the deployment.

      I tried to workaround this by renaming my ear to the runtime name and using that to replace the existing deployment but that gives this exception:

      Cannot upload deployment:

      {"domain-failure-description" => "WFLYCTL0216: Management resource '[(\"deployment\" => \"otherName.ear\")]' not found"}

              cmiranda@redhat.com Claudio Miranda
              dba2_jira Jeff Scott (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: