Bug 817815

Summary: webadmin [Task Manager]: please add tool tips to unknown task
Product: Red Hat Enterprise Virtualization Manager Reporter: Dafna Ron <dron>
Component: ovirt-engine-webadmin-portalAssignee: Einav Cohen <ecohen>
Status: CLOSED WONTFIX QA Contact: yeylon <yeylon>
Severity: high Docs Contact:
Priority: medium    
Version: 3.1.0CC: acathrow, dyasny, ecohen, iheim, Rhev-m-bugs, srevivo, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-23 09:20:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screen shot none

Description Dafna Ron 2012-05-01 12:15:16 UTC
Created attachment 581357 [details]
screen shot

Description of problem:

currently when we have a failure in jboss when a task is synchroniouse, the task manager will show the task with a question mark. 
please add a tool tip to tasks that are in unknown to say something like "task interrupted - status unknown"
I also suggest that we might consider changing the question mark to a different icon. 

currently a second bug will be opened for backend to remove single synchroniouse tasks if they become unknown from the UI, but tasks that will be part of a chain of command (like create storage domain + attach) will still be shown in the UI iin case of failure with unknown state. 

Version-Release number of selected component (if applicable):

si2.1

How reproducible:

100%

Steps to Reproduce:
1. deactivate storage domain 
2. while in image locked restart jboss
3.
  
Actual results:

task will become unknown and we only see the task as having a question mark

Expected results:

if we have no way of monitoring the synchroniouse tasks in case of failure we should have a better explanation in UI. 

Additional info: screen shot

Comment 1 Itamar Heim 2012-12-23 09:20:19 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.