Bug 1952555 - openshift-console logs flooded with 'websocket: bad handshake' and '403 Forbidden' errors
Summary: openshift-console logs flooded with 'websocket: bad handshake' and '403 Forbi...
Keywords:
Status: CLOSED DUPLICATE of bug 1848151
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Jakub Hadvig
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-22 14:38 UTC by Robert Sandu
Modified: 2024-06-14 01:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-22 14:51:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


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