Bug 828296 – No progress information for 'Scan for Updates' operation

Bug 828296 - No progress information for 'Scan for Updates' operation

Summary:	No progress information for 'Scan for Updates' operation

Status:	NEW

Aliases:	None

Product:	RHQ Project
Classification:	Other
Component:	Usability (Show other bugs)
Sub Component:
Version:	4.4
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified (vote)
Target Milestone:	---
Target Release:	---
Assigned To:	RHQ Project Maintainer
QA Contact:	Mike Foley
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-06-04 10:04 EDT by Filip Brychta
Modified:	2012-06-04 10:04 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Filip Brychta 2012-06-04 10:04:09 EDT

Description of problem:
No progress is displayed for Administration->Agent plugins->Scan for Updates operation. Operation can run for long time and user is not notified that operation is actually running.   

Version-Release number of selected component (if applicable):
Version: 3.1.0.CR1
Build Number: 4bc4270:1b85993

How reproducible:
Always

Steps to Reproduce:
1.copy a new version of some agent plugin to $JON_SERVER_HOME/plugins
2.click on Administration->Agent plugins->Scan for Updates
  
Actual results:
Operation is launched on the background but no visible notification is displayed. User can click on Scan for Updates button several times but nothing happens visually. 

Expected results:
Scanning in progress message, progress bar, disable Scan for Updates button or anything to let user know that operation was launched.

Note You need to log in before you can comment on or make changes to this bug.