Bug 887522 - Site did not correctly handle queued user
Summary: Site did not correctly handle queued user
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Clayton Coleman
QA Contact: libra bugs
URL:
Whiteboard:
: 887423 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-15 22:40 UTC by Clayton Coleman
Modified: 2015-05-15 01:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 23:09:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Clayton Coleman 2012-12-15 22:40:38 UTC
Over the weekend we hit our queue limit.  The site was not correctly handling and informing users that they were queued, which resulted in confused on the user's part.

The user had:

2012-12-15 14:53:11.774 [DEBUG] Streamline call (303.7ms) roles! /wapps/streamline/cloudVerify.html [ args: {}, code: 200, response: {"username"=>"XXXXXXXX", "roles"=>["simple_authenticated", "cloud_access_request_1"]} ] (pid:22675)

which means that all the hooks higher in the list failed to properly error the user out.  The broker was returning a standard 401 (which is a general failure in some cases).

Comment 1 Clayton Coleman 2012-12-18 15:16:13 UTC
*** Bug 887423 has been marked as a duplicate of this bug. ***

Comment 2 Clayton Coleman 2013-01-18 21:40:48 UTC
Very difficult to reproduce - without access to Streamline infrastructure.  QA can be verifying users can sign up and accept terms (regression test) rather than full functional verification.

Fixed in: https://github.com/openshift/li/pull/770

Comment 3 Yujie Zhang 2013-01-22 03:38:35 UTC
(In reply to comment #2)
Tested this issue on devenv_2705, user can sign up, accept terms, sign in and create application successfully, so verify this bug.


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