Uploaded image for project: 'Hawkular'
  1. Hawkular
  2. HAWKULAR-547

Removed archive displays in the deployment list with current state as failed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • 1.0.0.Alpha 13
    • 1.0.0.Alpha3
    • User Interface
    • None
    • Hide
      • Setup hawkular with inbuilt app server.
      • Login to Hawkular.
      • Navigate to Application Servers->Deployments' tab.
      • Select action 'Remove' for an archive ex: hawkular-alerts-actions-email.war
      • The success message appears in UI and server log
      • The current status shows 'failed'.
      • The archive is shown in the deployments tab and not removed.
      Show
      Setup hawkular with inbuilt app server. Login to Hawkular. Navigate to Application Servers->Deployments' tab. Select action 'Remove' for an archive ex: hawkular-alerts-actions-email.war The success message appears in UI and server log The current status shows 'failed'. The archive is shown in the deployments tab and not removed.

      From the Application Server's depolyments tab, if choosing action 'Remove' for an archive, the message in UI shows success and the server log also displays - "operationName":"Remove","status":"OK".

      The current status of the archive shows 'failed' state however the archive remains in the deployments list.

      Logging the ticket to ensure if this is the correct behaviour or if the archive should not be displayed in the deployments list.

        1. Screenshot_RemovedArchive_shown-In-DeploymentsList.png
          Screenshot_RemovedArchive_shown-In-DeploymentsList.png
          86 kB
        2. Screenshot-RemoveArchive.png
          Screenshot-RemoveArchive.png
          6 kB

            alexandrem_jira Alexandre Mendonça (Inactive)
            skondkar1@redhat.com Sunil Kondkar (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: