Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 588509 - EWS: Cannot delete war content from Content tab
EWS: Cannot delete war content from Content tab
Product: RHQ Project
Classification: Other
Component: Plugins (Show other bugs)
All Windows
high Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Corey Welton
Depends On:
Blocks: jon24-ews
  Show dependency treegraph
Reported: 2010-05-03 16:30 EDT by Corey Welton
Modified: 2011-03-08 08:20 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-03-08 08:20:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Corey Welton 2010-05-03 16:30:42 EDT
Description of problem:
When attempting to delete war info from within the Content tab, user gets a fail message with apparently no context.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.  Assure your tomcat/EWS server is inventoried and has gone green
2.  Navigate to your virtual host; deploy a .war file (i.e., counter.war)
3.  Once it has gone green, navigate to the resource in the tree (i.e., counter/)
4.  Click the Content tab; select your resource from within the table and click "Delete"
5. View results
Actual results:
Audit trail indicates that deletion failed, but offers no context as to why.

Expected results:
User can delete and/or find out why the failure occurred.

Additional info:
User can still delete actual war deployments from appropriate inventory tab in parent resource.
Comment 1 Charles Crouch 2011-03-08 08:20:55 EST
Deleting WAR entries from the Content tab is not support, as mentioned in the description the supported way of doing this is via the Inventory tab in the parent resource.

Note You need to log in before you can comment on or make changes to this bug.