Bug 535020 (RHQ-175) - Investigate running a resource discovery scan after a successful package installation
Summary: Investigate running a resource discovery scan after a successful package inst...
Keywords:
Status: CLOSED DUPLICATE of bug 535064
Alias: RHQ-175
Product: RHQ Project
Classification: Other
Component: Content
Version: 1.0
Hardware: All
OS: All
high
medium
Target Milestone: ---
: ---
Assignee: Jason Dobies
QA Contact:
URL: http://jira.rhq-project.org/browse/RH...
Whiteboard:
Depends On: RHQ-144
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-24 19:36 UTC by Jessica Sant
Modified: 2009-11-11 17:20 UTC (History)
0 users

Fixed In Version: 1.0
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
r387, r9721
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description Jessica Sant 2008-03-24 19:36:00 UTC 
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.
Comment 1 Ian Springer 2008-03-24 19:55:50 UTC 
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.
Comment 2 Charles Crouch 2008-03-24 20:02:56 UTC 
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.
Comment 3 Jason Dobies 2008-03-25 13:31:23 UTC 
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.
Comment 4 Jason Dobies 2008-03-25 14:11:23 UTC 
This is effectively a duplicate of RHQ-179.
Comment 5 Joseph Marques 2008-06-17 21:09:00 UTC 
this was resolved as a duplicate of another issue, no testing needed.
Comment 6 Red Hat Bugzilla 2009-11-10 20:46:04 UTC 
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.
Comment 7 David Lawrence 2009-11-11 17:20:53 UTC 

*** This bug has been marked as a duplicate of bug 535064 ***
Note You need to log in before you can comment on or make changes to this bug.