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

Bug 1940706

Summary:	[4.5] - User is getting logged out intermediately - from kube-apiserver I see - the server is currently unable to handle the request
Product:	OpenShift Container Platform	Reporter:	Vladislav Walek <vwalek>
Component:	apiserver-auth	Assignee:	Standa Laznicka <slaznick>
Status:	CLOSED DUPLICATE	QA Contact:	pmali
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.5	CC:	aos-bugs, mfojtik, slaznick
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-03-24 17:36:31 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:

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.