Bug 714785

Summary: perform discovery after a bundle deployment
Product: [Other] RHQ Project Reporter: John Mazzitelli <mazz>
Component: ProvisioningAssignee: Thomas Segismont <tsegismo>
Status: CLOSED DUPLICATE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0.1CC: hrupp, tsegismo
Target Milestone: ---   
Target Release: RHQ 4.13   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-10 10:41:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Mazzitelli 2011-06-20 18:32:03 UTC 
After deploying a bundle to a resource, we should run a discovery on that resource to see if the bundle deployment created new servers or services.

We need to be careful about the timings - immediately after a bundle deployment, the new resource may not be available yet (for example, if you deploy a war, you need to wait for the JBossAS server's URL scanner to wake up and find the war and deploy it. This could take several seconds to several minutes.
Comment 1 Thomas Segismont 2014-09-10 10:41:51 UTC 

*** This bug has been marked as a duplicate of bug 970784 ***