Bug 1331854 - [RFE] Improve error message in case the engine does not report back in a timely manner
Summary: [RFE] Improve error message in case the engine does not report back in a time...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.Core
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: Scott Dickerson
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-29 20:01 UTC by movciari
Modified: 2019-04-28 14:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-15 12:19:00 UTC
oVirt Team: UX
oourfali: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

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

Description movciari 2016-04-29 20:01:16 UTC 
Description of problem:
When you load webadmin or userportal and then engine goes down, it should warn the user with a notification. 

This can be achieved by checking the healthpage whenever query hits the timeout (or periodically)

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


How reproducible:
always

Steps to Reproduce:
1. Open webadmin or userportal
2. stop ovirt-engine
3. change webadmin tab or try to perform any action

Actual results:
progress animation is being displayed forever

Expected results:
should wait for timeout and then tell you engine is not running

Additional info:
Comment 1 Yaniv Kaul 2016-05-01 06:39:04 UTC 
I think it's a rare enough occurrence (outside of testing environment) that I don't think it's worth the effort implementing this. I do agree that the generic exception could be improved to provide text with 'please verify the engine is running'.
Comment 2 Oved Ourfali 2017-05-15 12:19:00 UTC 
I agree with Yaniv this is quite rare, and not straight forward.
Closing as wontfix.
Note You need to log in before you can comment on or make changes to this bug.