Bug 822228

Summary: "discovery -f" should abort if a discovery scan is already in progress
Product: [Other] RHQ Project Reporter: Ian Springer <ian.springer>
Component: AgentAssignee: Charles Crouch <ccrouch>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4CC: ccrouch, hbrock, hrupp
Target Milestone: ---   
Target Release: RHQ 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: 4.5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-01 06:12:19 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Ian Springer 2012-05-16 13:39:53 EDT
Otherwise, "discovery -f" will take up to twice as long to return, while it waits for the currently running scan to complete and then kicks off a new scan and waits for that to complete. That could be confusing or frustrating to users.
Comment 1 Ian Springer 2012-05-16 14:22:31 EDT
Done in master:

Comment 4 Heiko W. Rupp 2013-09-01 06:12:19 EDT
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.