Bug 829227 - Failed to rename illegitimate plugin during upgrade.
Summary: Failed to rename illegitimate plugin during upgrade.
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-06 09:18 UTC by Filip Brychta
Modified: 2022-03-31 04:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 818673 0 urgent CLOSED [as7] rename the as7 plugin from "jboss-as-7" to "JBossAS7" 2021-02-22 00:41:40 UTC

Internal Links: 818673

Description Filip Brychta 2012-06-06 09:18:04 UTC
Description of problem:
Harmless but unnecessary error messages are thrown to agent log during upgrade.

Version-Release number of selected component (if applicable):
jon3.1.0.RC2

How reproducible:
Always

Steps to Reproduce:
1.follow upgrade procedure and upgrade JON.3.0.1.GA + some agent plugins to JON.3.1.0 
2. check the agent.log
  
Actual results:
similar messages (depends on what agent plugins was installed) are thrown to agent.log 
2012-06-05 14:38:36,775 WARN  [RHQ Server Polling Thread] (org.rhq.enterprise.agent.PluginUpdate)- {PluginUpdate.plugin-not-on-server}The plugin [plugins/rhq-agent-plugin-4.2.0.JON.3.0.1.GA.jar] does not exist on the Server - renaming it to [rhq-agent-plugin-4.2.0.JON.3.0.1.GA.jar.REJECTED] so it will not get deployed by the Plugin Container.
2012-06-05 14:38:36,775 ERROR [RHQ Server Polling Thread] (org.rhq.enterprise.agent.PluginUpdate)- {PluginUpdate.plugin-rename-failed}Failed to rename illegitimate plugin [plugins/rhq-agent-plugin-4.2.0.JON.3.0.1.GA.jar] to [rhq-agent-plugin-4.2.0.JON.3.0.1.GA.jar.REJECTED]. 

Expected results:
This is expected scenario (the old plugins are not available in upgraded system) so the ERROR log level is not necessary.


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