Bug 684765 - Plugins not being deleted from server after purge (in HA?)
Summary: Plugins not being deleted from server after purge (in HA?)
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 4.0.0.B02
Hardware: Unspecified
OS: Unspecified
unspecified vote
Target Milestone: ---
: ---
Assignee: John Sanda
QA Contact: Corey Welton
Depends On:
Blocks: rhq4 gwt-plugins
TreeView+ depends on / blocked
Reported: 2011-03-14 13:02 UTC by Corey Welton
Modified: 2011-10-04 19:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-05-24 01:09:18 UTC

Attachments (Terms of Use)

Description Corey Welton 2011-03-14 13:02:07 UTC
Description of problem:
After deleting and purging plugins, the files are not being physically removed from the server.  This is in an HA configuration, but that might actually be a red herring.

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

How reproducible:

Steps to Reproduce:
1.  Install two RHQ servers in an HA configuration
2.  Administration > Plugins
3.  Delete the IRC agent plugin
4.  Purge the deleted plugin
5.  Observe that the plugin has disappeared from the UI.
6.  Wait some time and view the plugins directory on both servers
Actual results:
The plugin remains on the filesystem(s)

Expected results:
The plugin gets deleted.

Additional info:
As noted, I'm not sure whether or not this is an artifact of the HA configuration. But plugins have gotten deleted before just fine.

Comment 1 John Mazzitelli 2011-03-25 18:31:07 UTC
i think john sanda just fixed this (or something close to this) recently.

assigning to john to close if appropriate or to comment if its still a problem

Comment 2 John Sanda 2011-03-25 18:34:58 UTC
I am moving this to ON_QA because I believe that the fix for bug 683545 addresses this as well.

Comment 3 Mike Foley 2011-05-02 18:37:22 UTC
deleted and purged plugins, they remain deleted.  rhq 4.0 rc2

Comment 4 Corey Welton 2011-05-24 01:09:18 UTC
Bookkeeping - closing bug - fixed in recent release.

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