Red Hat Bugzilla – Bug 1302946
Sometime can't get token when access token/request api in v3 stage env
Last modified: 2016-02-23 15:31:55 EST
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.
Steps to Reproduce:
1.In web access token request url
1.Error getting token: Invalid status code (400): 400 Bad Request
1.Get token success
What is in the master logs when this occurs?
(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
*** Bug 1304099 has been marked as a duplicate of this bug. ***
Fix upstream in https://github.com/openshift/origin/pull/6982/
This bug test block our v3 stage test, high this bug.
That token can be taken to the console for testing.
We have deployed a hotfix it should be working now.
Verified this bug against v3 stage,now we could get token via accessing oauth/token/request page.
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.
*** Bug 1306351 has been marked as a duplicate of this bug. ***
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.