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   
Whiteboard:
Fixed In Version: 4.5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-01 10:12:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ian Springer 2012-05-16 17:39:53 UTC
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 18:22:31 UTC
Done in master:

http://git.fedorahosted.org/git?p=rhq/rhq.git;a=commitdiff;h=15d7dca

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