Red Hat Bugzilla – Bug 828329
Allow to run an discovery scan upon successful operation completion
Last modified: 2013-09-01 05:59:55 EDT
When e.g. a user deploys a file to a as7-domain deployment and then uses the
operation "deploy to server group", the resulting deployment on server group
level will only be visible after the next discovery scan, which can be hours
We should offer to trigger a discovery scan on successful completion of an
operation, like we do after create child resources.
This could be triggered by an attribute on the <operation> element, which is
only read by the agent plugin container.
Here is another use case where this problem is more obvious:
1) Install EAP6 Standalone (NO manual configuration to setup RHQ user)
2) Discover and inventory the EAP6 server
3) Run "Install RHQ user" operation on the EAP6 server
4) Check server availability and browser sub-resources
Server becomes available, and all the sub-services are discovered immediately.
The server becomes available however, no sub-resources are discovered immediately. All sub-resources will be discovered when the next discovery process runs.
This can give the wrong impression that the EAP6 server is not inventoried correctly since the next discovery process could run 24 hours after the server is configured to work with RHQ.
*** Bug 844219 has been marked as a duplicate of this bug. ***
Stefan, can you comment on where your investigation went with this.
JON 3.1.1 ER1 build is available. Moving to ON_QA.
Moving back to ON_DEV. This was incorrectly moved to ON_QA in comment 4.
Added the possibility to start discovery scans from a resource context. The code executes a service scan for children of the resource linked to the resource context.
master branch commits:
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.