-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
None
-
False
-
None
-
False
-
Testable
-
No
-
-
-
-
-
-
-
1.23.0
-
No
-
No
-
Pending
-
None
-
-
-
RHODS 1.23
Description of problem:
UPDATE
the complete fix is going to be tracked by RHODS-7505
When running the scale test bare-metal with 1000 users, I observe some instabilities of the oauth-proxy container:
The previous logs of the oauth-proxy containers are full of these messages:
$ oc logs rhods-dashboard-659c6bfddf-mdwzg --previous -c oauth-proxy
2023/01/23 09:32:42 reverseproxy.go:485: http: proxy error: context canceled
2023/01/23 09:32:44 reverseproxy.go:485: http: proxy error: context canceled
2023/01/23 09:32:44 server.go:3120: http: TLS handshake error from 10.130.0.1:43350: write tcp 10.130.14.234:8443->10.130.0.1:43350: write: broken pipe
2023/01/23 09:32:44 provider.go:587: Performing OAuth discovery against https://172.30.0.1/.well-known/oauth-authorization-server
2023/01/23 09:32:44 server.go:3120: http: TLS handshake error from 10.130.0.1:43372: write tcp 10.130.14.234:8443->10.130.0.1:43372: write: broken pipe
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
- Run the RHODS-notebook scale test with 1000 users (3s delay) trying to access the Dashboard
Actual results:
many user tests fail with this error:
and messages like this one in the browser logs:
{'level': 'SEVERE', 'message': 'https://rhods-dashboard-redhat-ods-applications.apps.bm.example.com/api/segment-key - Failed to load resource: the server responded with a status of 503 (Service Unavailable)', 'source': 'network', 'timestamp': 1674466086292}]
or this one:
Expected results:
Reproducibility (Always/Intermittent/Only Once):
Build Details:
rhods-operator.1.21.0-20
Workaround:
Additional info:
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-
- mentioned on
