Bug 1367921

Summary: [AAA] "Request state does not match session state" after successful login
Product: [oVirt] ovirt-engine Reporter: Greg Sheremeta <gshereme>
Component: AAAAssignee: Ravi Nori <rnori>
Status: CLOSED CURRENTRELEASE QA Contact: Gonza <grafuls>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0.0CC: bugs, mgoldboi, mperina, pstehlik, rhodain
Target Milestone: ovirt-4.0.4Flags: rule-engine: ovirt-4.0.z+
mgoldboi: planning_ack+
mperina: devel_ack+
pstehlik: testing_ack+
Target Release: 4.0.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-26 12:34:22 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:
Embargoed:
Attachments:
Description Flags
request_state none

Description Greg Sheremeta 2016-08-17 19:41:25 UTC
Created attachment 1191737 [details]
request_state

Description of problem:
[AAA] "Request state does not match session state" after successful login *after* a session timeout, i.e. the first time after a timeout.

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

How reproducible:
?

Steps to Reproduce:
1. login to engine
2. let the engine sit and time out -- you'll see the login screen again. It's ok to switch to another tab for an hour or something
3. login to the engine with valid credentials

Actual results:
Error page: Request state does not match session state

Expected results:
successful login

Additional info:

Comment 1 Martin Perina 2016-08-19 05:12:42 UTC
Moving to POST as we need backport to ovirt-engine-4.0 branch

Comment 2 Greg Sheremeta 2016-08-19 11:32:37 UTC
*** Bug 1368111 has been marked as a duplicate of this bug. ***

Comment 3 Gonza 2016-09-13 14:55:00 UTC
Verified with:
rhevm-4.0.3-0.1.el7ev.noarch

User succesfully logged back in after timeout.