Red Hat Bugzilla – Bug 535020
Investigate running a resource discovery scan after a successful package installation
Last modified: 2009-11-11 12:20:53 EST
After a new patch is deployed through the content system, a discovery scan should be executed so that the new version string will be picked up.
NOTE: For now, the workaround is to either wait for the next scheduled server scan to run, or to execute the "discovery -f" Agent prompt command.
We should do this since without it the user will be able to see the old list of patches (which includes the patch they just applied) for the JBAS instance. They may attempt to re-apply the same patch again which would be bad.
A package discovery scan is triggered after a package is installed, but not a resource discovery. I'm hesitant to add that, but I'll look into it.
This is effectively a duplicate of RHQ-179.
this was resolved as a duplicate of another issue, no testing needed.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-175
This bug was marked DUPLICATE in the database but has no duplicate of bug id.
*** This bug has been marked as a duplicate of bug 535064 ***