Bug 813847 - Login page: when connection to the backend is lost, no error message is displayed
Summary: Login page: when connection to the backend is lost, no error message is displ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Einav Cohen
QA Contact:
URL:
Whiteboard: infra ux
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-18 15:06 UTC by Pavel Novotny
Modified: 2016-01-28 21:54 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-19 00:41:29 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description Pavel Novotny 2012-04-18 15:06:29 UTC
Description of problem:
If you are on the login screen and you stop jboss backend (or it crashes), no error message is displayed. If you then submit the form with username and password filled, the form fields get grayed out (as it is processing the data) and stays like that forever.

Version-Release number of selected component (if applicable):
ovirt-engine-3.0.0_0001-1.6.fc16.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Open oVirt webadmin login screen.
2. 
  2a) Kill your network connection to the oVirt machine (unplug cable, iptables, ...).
  or
  2b) Stop jboss server on oVirt machine.
3. Fill in username, password and submit.
  
Actual results:
Form fields get grayed out as usual, but they stay this way forever.

Expected results:
After a while (connection timeout), some error message about lost connection is displayed.

Additional info:

This problem is only on login page. When user is already logged in and hit connection or jboss issue, error dialog pops out with message: "Error: A Request to the Server failed with the following Status Code: 0".

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


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