-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
RHODS_1.20.0_GA
-
False
-
None
-
False
-
Testable
-
No
-
-
-
-
-
-
-
No
-
No
-
Pending
-
None
-
-
Problem observed:
- as part of our Notebook scale testing, with 300 users starting with 3s delay (user-level testing).
- with the API-level notebook scale testing, with 20 users continuously launching and destroying notebooks within 10 minutes.
Description of problem:
After logging into JupyterLab, an empty page is shown.
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
- Launch a notebook (Data Science image) and wait for it to be ready
- Log in into it and authorize the service account access
It's not 100% clear to me if the issue happens before or after Step 2.
Actual results:
- With ODS-CI (user-level): JupyterLab returns an empty page.
- With Locust (API-level): JupyterLab returns an empty response (no HTTP code, no content)
Expected results:
The JupyterLab logo and page show up
Reproducibility (Always/Intermittent/Only Once):
Only in the scale test.
The locust (API-level) scale test can be easily executed locally, the issue appears often enough.
Build Details:
Workaround:
Reload the page.
Additional info:
- is related to
-
RHOAIENG-1576 [DSG] JupyterLab/Oauth not available after clicking the `open` button
- Backlog