Bug 1940706 - [4.5] - User is getting logged out intermediately - from kube-apiserver I see - the server is currently unable to handle the request
Summary: [4.5] - User is getting logged out intermediately - from kube-apiserver I see...
Keywords:
Status: CLOSED DUPLICATE of bug 1825219
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: apiserver-auth
Version: 4.5
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Standa Laznicka
QA Contact: pmali
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-18 23:33 UTC by Vladislav Walek
Modified: 2021-03-24 17:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-24 17:36:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Vladislav Walek 2021-03-18 23:33:53 UTC
Description of problem:

IHAC, where the user is being logged out after random period of time. 
Same for console and command line tools.

The user after a while (within 1 - 10min) after running command with "oc" cli it shows error - Unauthorized.

I checked the logs and I see following:

From kube-apiserver:
authentication.go:53] Unable to authenticate the request due to an error: [invalid bearer token, the server is currently unable to handle the request (get users.user.openshift.io <username>)

From apiserver (where <IP> is IP of one of the masters)
log.go:172] http: TLS handshake error from <IP>:35548: EOF


The strange behavior is also that only 1 master shows logs, the other 2 seems like they are not accessed.

Version-Release number of selected component (if applicable):
OpenShift Container Platfrom 4.5.18
IPI on Azure

How reproducible:
The issue is reproducible on customer side only.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
additional info will be provided next

Comment 2 Standa Laznicka 2021-03-19 09:03:14 UTC
The user is not logged out, only one of the apiservers fails to respond. Possibly an issue with the node's network, possibly P&F, although I am not sure. There are no attachments to the case in supportshell and I have no idea what flopbox is. Please provide a must-gather.


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