Bug 1765733

Summary: [Feature:OAuthServer] [Token Expiration] Using a OAuth client with a non-default token max age to generate tokens that do not expire works as expected when using a code authorization flow
Product: OpenShift Container Platform Reporter: Anurag saxena <anusaxen>
Component: apiserver-authAssignee: Standa Laznicka <slaznick>
Status: CLOSED ERRATA QA Contact: scheng
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, huirwang, mfojtik, nagrawal, slaznick
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-23 11:09:38 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:
Bug Depends On:    
Bug Blocks: 1791855    

Description Anurag saxena 2019-10-25 20:11:06 UTC
Description of problem:
fail [github.com/openshift/origin/test/extended/oauth/expiration.go:30]: Unexpected error:
    <*errors.errorString | 0xc00027c100>: {
        s: "timed out waiting for the condition",
    timed out waiting for the condition

Additional info:

Comment 1 Michal Fojtik 2019-11-06 13:21:09 UTC
*** Bug 1764408 has been marked as a duplicate of this bug. ***

Comment 2 Michal Fojtik 2019-11-06 13:21:14 UTC
*** Bug 1765734 has been marked as a duplicate of this bug. ***

Comment 4 Neelesh Agrawal 2019-11-27 19:44:14 UTC
Still see these failures ~15% of the times:
Can this be fixed in 4.3 timeframe?

Comment 5 Standa Laznicka 2019-11-28 07:54:40 UTC
There's a patch already for master, just waiting for it to merge so that we can backport it to 4.3 - https://github.com/openshift/origin/pull/24217

Comment 10 errata-xmlrpc 2020-01-23 11:09:38 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.