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

Bug 1952555

Summary:	openshift-console logs flooded with 'websocket: bad handshake' and '403 Forbidden' errors
Product:	OpenShift Container Platform	Reporter:	Robert Sandu <rsandu>
Component:	Management Console	Assignee:	Jakub Hadvig <jhadvig>
Status:	CLOSED DUPLICATE	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.6	CC:	aos-bugs, jokerman, nbharti, spadgett
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-04-22 14:51:04 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 Robert Sandu 2021-04-22 14:38:31 UTC

Description of problem: openshift-console pod logs are actively flooded with 'websocket: bad handshake.*403 Forbidden' errors.

Sample log:

2021-03-31T08:30:01.118826164Z 2021-03-31T08:30:01Z Failed to dial backend: 'websocket: bad handshake' Status: '403 Forbidden' URL: 'https://kubernetes.default.svc/apis/config.openshift.io/v1/clusterversions?watch=true&fieldSelector=metadata.name%3Dversion'

Version-Release number of selected component (if applicable): 4.6.22

How reproducible: not manually reproducible

Actual results: openshift-console logs flooded with 100.000+ noisy `websocket: bad handshake` errors, in only 4 weeks. 

Expected results: reduced log noise while relying on `consoles.spec.logLevel: Normal` verbosity.

Additional info:
- No impact on Console access, but log noise leads to losing valuable information.

Comment 2 Samuel Padgett 2021-04-22 14:51:04 UTC

This is a side effect of bug 1848151 where we were polling the ClusterVersion when the user didn't have authority. It creates a lot of noise in the logs and something we've fixed, but otherwise it should cause no problems.

*** This bug has been marked as a duplicate of bug 1848151 ***