Bug 1007403

Summary: horizon [Havana]: unclear error when trying to launch instance after session expired
Product: Red Hat OpenStack Reporter: Dafna Ron <dron>
Component: python-django-horizonAssignee: Matthias Runge <mrunge>
Status: CLOSED ERRATA QA Contact: Ami Jeain <ajeain>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0CC: aortega, ddomingo, hateya, jpichon, mrunge, yeylon
Target Milestone: rc   
Target Release: 4.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: python-django-horizon-2013.2-3.el6ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-20 00:24:22 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:
Attachments:
Description Flags
logs none

Description Dafna Ron 2013-09-12 12:24:24 UTC
Created attachment 796834 [details]
logs

Description of problem:

if we try to launch and instance after session has expired we get the following error: 
Error: An error occurred. Please try again later.

only after we move between the tabs we are logged out 

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

python-django-horizon-2013.2-0.10b3.el6.noarch

How reproducible:

100%

Steps to Reproduce:
1. select the instance tab under Admin tab
2. let the session expire 
3. try to launch an instance 

Actual results:

we get: Error: An error occurred. Please try again later. instead of user being logged out

Expected results:

we should log out the expired session or add a more informative error 

Additional info:

Comment 2 Matthias Runge 2013-10-01 07:31:28 UTC
Should be fixed in rc1, we have currently no build.

Comment 3 Matthias Runge 2013-11-13 10:51:37 UTC
The situation shouldn't be reproducible at all.

Comment 5 Ami Jeain 2013-11-21 10:18:27 UTC
verified it works properly in the latest puddle (RHOS beta).
no error, just relogin page

Comment 7 Matthias Runge 2013-12-10 07:26:46 UTC
no docs required here.

Comment 9 errata-xmlrpc 2013-12-20 00:24:22 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2013-1859.html