Red Hat Bugzilla – Bug 838153
The agent running in background is stopped after removing plugins with types in inventory.
Last modified: 2013-09-11 07:03:06 EDT
+++ This bug was initially created as a clone of Bug #828938 +++
Created attachment 589558 [details]
Description of problem:
The agent running on the background is stopped after removing jBossAS7 plugin from jon.
Version-Release number of selected component (if applicable):
Build Number: 05c820d:aaa5a79
Steps to Reproduce:
1.Clean installation of jon3.1.0.CR2 + jon-plugin-pack-eap-3.1.0.CR2 is running, eap6 running and imported to jon inventory, the rhq agent is running on the background
2.go to administration>agent plugins
3.disable jBossAS7 plugin
4.delete jBossAS7 plugin
The agent is stopped.
The agent is running.
--- Additional comment from email@example.com on 2012-07-02 09:04:05 EDT ---
I've reproduced this with JON 3.1.0.GA AS7 and Postgres plugins. Although the agent was unaffected when deleting plugins that were not being used(Ex. IIS plugin on Linux box). Not sure if that's relevant yet. Moving this to ON_DEV.
--- Additional comment from firstname.lastname@example.org on 2012-07-02 09:07:09 EDT ---
A few more data points.
- Doesn't seem to happen when agent is running in console mode.
- After background agent goes down if you restart the agent it seems then operate unaffected.
--- Additional comment from email@example.com on 2012-07-03 16:59:34 EDT ---
This is fixed with commit 0a0c9a990684675c to master.
Leaving this ON_DEV as this commit needs to be cherrypicked to the release branch for 3.1.1 still.
--- Additional comment from firstname.lastname@example.org on 2012-07-05 09:12:09 EDT ---
Another update(typo and thread identification) for this issue to master with commit 21ca86fc1c1be1d5c41089.
Updated title to reflect how this issue is not exclusively related to AS7 specifically but to any plugins where types have been imported into inventory and then later deleted.
Cloned to track QA verification for master branch. Moving this to ON_QA as already fixed in master as indicated above.
This should not have been moved to ON_QA. Should have been in NEW state for confirmation of triage into 3.1.1. This still needs to be cherry-picked to release branch.
Moving this to JBoss ON product bug tracker considering it somehow slipped through the cracks in the 3.1.0 release.
This has been cherry-picked to the release branch with commit:
Moving this to MODIFIED.
Moving to ON_QA as new build available to test with:
Verified on 3.1.2.ER5