Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1302946

Summary:	Sometime can't get token when access token/request api in v3 stage env
Product:	OpenShift Container Platform	Reporter:	DeShuai Ma <dma>
Component:	apiserver-auth	Assignee:	Jordan Liggitt <jliggitt>
Status:	CLOSED ERRATA	QA Contact:	weiwei jiang <wjiang>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.1.0	CC:	agrimm, aos-bugs, bleanhar, dma, erjones, jliggitt, lxia, misalunk, whearn, wsun
Target Milestone:	---	Keywords:	TestBlocker
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-23 20:31:55 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:
Bug Depends On:
Bug Blocks:	1303130

Description DeShuai Ma 2016-01-29 05:57:22 UTC

Description of problem:
Can't request token in v3 stage env, always return error "Error getting token: Invalid status code (400): 400 Bad Request"

Version-Release number of selected component (if applicable):
latest stage env.

How reproducible:
sometime

Steps to Reproduce:
1.In web access token request url
https://<stage_api_server>/oauth/token/request

Actual results:
1.Error getting token: Invalid status code (400): 400 Bad Request 

Expected results:
1.Get token success

Additional info:

Comment 1 Jordan Liggitt 2016-01-29 16:43:22 UTC

What is in the master logs when this occurs?

Comment 2 DeShuai Ma 2016-02-01 01:31:34 UTC

(In reply to Jordan Liggitt from comment #1)
> What is in the master logs when this occurs?

We can't get the master logs, the env is provided by ops, we have no permission to access the master and node. When test on the env, this happened very often

Comment 3 Jordan Liggitt 2016-02-02 21:33:30 UTC

*** Bug 1304099 has been marked as a duplicate of this bug. ***

Comment 4 Jordan Liggitt 2016-02-02 22:20:14 UTC

Fix upstream in https://github.com/openshift/origin/pull/6982/

Comment 5 DeShuai Ma 2016-02-03 06:04:36 UTC

This bug test block our v3 stage test, high this bug.

Comment 6 Jordan Liggitt 2016-02-03 06:08:21 UTC

Until the fix is deployed, you can get a token by logging into the web console and running this in the javascript console:

prompt("Token",localStorage["LocalStorageUserStore.token"])

That token can be taken to the console for testing.

Comment 7 Wesley Hearn 2016-02-03 22:07:01 UTC

We have deployed a hotfix it should be working now.

Comment 8 Wei Sun 2016-02-04 02:21:56 UTC

Verified this bug against v3 stage,now we could get token via accessing oauth/token/request page.

Comment 10 Jordan Liggitt 2016-02-05 20:30:37 UTC

Fix is in OSE in https://github.com/openshift/ose/commit/5d69528c759aceaed3ce3bebcee3da6deedd7592

I think that means it will be in the next 3.1.x update.

Comment 11 Miheer Salunke 2016-02-11 08:53:49 UTC

*** Bug 1306351 has been marked as a duplicate of this bug. ***

Comment 14 errata-xmlrpc 2016-02-23 20:31:55 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.

https://access.redhat.com/errata/RHBA-2016:0293