Bug 1320498

Summary: All long-running tasks should be reported in Tasks tab
Product: [oVirt] ovirt-engine Reporter: Yedidyah Bar David <didi>
Component: Backend.CoreAssignee: Nobody <nobody>
Status: CLOSED NOTABUG QA Contact: Pavel Stehlik <pstehlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.6.1CC: bugs, oourfali, sbonazzo
Target Milestone: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-24 11:11:05 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:
Bug Depends On:    
Bug Blocks: 1306356    

Description Yedidyah Bar David 2016-03-23 10:56:00 UTC 
Description of problem:

Sometimes tasks take a long time. Some of them appear in the Tasks tab in the admin web interface. Some do not. This might be due to bugs. It can also be because it was expected that they'll only take a short time, thus were not added there, but in reality they took longer.

All long-running tasks should appear in the Tasks tab, after some time, say 20 seconds (or a configurable amount). This should be done in a general way, so that no type-specific code will have to be added to tasks that do not appear there yet, but include enough relevant information to help the user understand what's taking long, and why, if possible.
Comment 1 Oved Ourfali 2016-03-24 11:11:05 UTC 
You need to open it per task, and put on the different teams.
The different verticals need to define what they want to put there and what not, how to call it, and etc.

Please open a bug per something you saw is missing.
Comment 2 Yedidyah Bar David 2016-03-24 12:52:17 UTC 
(In reply to Oved Ourfali from comment #1)
> You need to open it per task, and put on the different teams.

Why?

Can't we have something general, that will always work?

If a task is handled by team and reported, nothing else to do. Otherwise, report something. Perhaps generic, but still more than nothing.
Comment 3 Oved Ourfali 2016-03-24 13:10:39 UTC 
(In reply to Yedidyah Bar David from comment #2)
> (In reply to Oved Ourfali from comment #1)
> > You need to open it per task, and put on the different teams.
> 
> Why?
> 
> Can't we have something general, that will always work?
> 
> If a task is handled by team and reported, nothing else to do. Otherwise,
> report something. Perhaps generic, but still more than nothing.

The design of the tasks you see in the UI is based on commands defining what you see, based on their flow.
It can be an async VDSM task, a set of 3 engine commands that take a while, contacting an external source such as Satellite, and etc.
A task isn't a specific task. It is a "logic" task.
It is defined by the command, represented by the command, etc...