Bug 813847

Summary: Login page: when connection to the backend is lost, no error message is displayed
Product: [Retired] oVirt Reporter: Pavel Novotny <pnovotny>
Component: ovirt-engine-webadminAssignee: Einav Cohen <ecohen>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, bazulay, dyasny, ecohen, iheim, mgoldboi, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra ux
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-19 00:41:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.