Bug 542755

Summary:	Unable to redeploy a previously undeployed server side plugin
Product:	[Other] RHQ Project	Reporter:	wes hayutin <whayutin>
Component:	Plugin Container	Assignee:	John Mazzitelli <mazz>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Corey Welton <cwelton>
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	ckannan, cwelton
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://10.16.120.193:7080/rhq/admin/plugin/plugin-list.xhtml
Whiteboard:
Fixed In Version:	2.4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-08-12 16:49:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	542757

Description wes hayutin 2009-11-30 17:57:48 UTC

version:
commit fff2771d008518f57516efb2607e9b1704973fb3

Description of problem:

Unable to deploy a server side plugin
I attempted to undeploy then redeploy the 
rhq-serverplugin-yum-1.4.0-SNAPSHOT.jar plugin.



Steps to Reproduce:
1. Check the yum server side plugin, and click undeploy.  The server side plugin is successfully removed
2.try to upload the rhq-serverplugin-yum-1.4.0-SNAPSHOT.jar or copy it to the <server-install-dir>/plugins directory
3. click scan for updates
  
Actual results:

no new plugins are found


Expected results:

The yum plugin is found and deployable 


Additional info:

Comment 1 John Mazzitelli 2009-12-02 16:42:34 UTC

there is code and unit tests that allow us to support this functionality. I didn't know how best to do it in the UI, so right now, you can't do it in the core UI, aside from the test "control.jsp" page. Go to the admin/test/control.jsp page and you'll have an option to purge a plugin completely - once purged from the database, you can redeploy the plugin again. This is only for testing during development - we need to come up with a way to officially do it in the UI. Perhaps have a page called "Previously Undeployed Plugins" and have an option to "resurrect" those plugins.

Comment 2 John Mazzitelli 2009-12-02 21:55:49 UTC

this is fixed now. the plugin UI page lets you show undeployed plugins. If you ever mistakenly undeploy a plugin (or you undeployed but want to later re-deploy it), you first must "purge" that plugin. So the UI lets you purge an undeployed plugin. At that point, you can file-upload a new plugin or you can just copy your new replacement plugin in the /plugins directory.

This is checked into the pc branch, merge with master will come soon.

Comment 3 John Mazzitelli 2010-01-28 15:45:42 UTC

this is in master.

use the "view undeployed" and then "purge" the old plugin. Once you purged a plugin (meaning, tell the server to completely forget it ever existed), you can upload a new one.

Remember, undeploying a plugin is usually only done when you want to tell a server to never deploy that plugin ever again. If you are looking to upgrade a plugin, just redeploy the new plugin or disable the plugin and upgrade it later when you want to. The purpose of undeploy is to tell all RHQ servers to completely remove a plugin and never deploy it again. This purge facilitate is really here to allow a user to "undo" an undeploy if they accidentally undeploy something or if they want to resurrect the usage of a plugin that they originally thought they didn't want anymore.

Comment 4 Corey Welton 2010-03-23 15:21:20 UTC

QA Verified.  The "Purge"  step is a bit tricky - we need to make sure this is clearly doc'd somewhere - but purging an undeployed plugin, copying it back and scanning for updates does result in the plugin successfully redeploying.

Comment 5 Corey Welton 2010-08-12 16:49:26 UTC

Mass-closure of verified bugs against JON.