Red Hat Bugzilla – Bug 822228
"discovery -f" should abort if a discovery scan is already in progress
Last modified: 2015-02-01 18:28:10 EST
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.
Done in master:
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.