-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
In Progress
-
Bug Fix
-
Before this update, Node log length was not limited. In the case of an extremely large log, this could result in the log not displaying and/or the browser crashing. This update limits a Node log's length to 1000 lines so the log displays correctly.
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-63470. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-62483. The following is the description of the original issue:
—
Description of problem:
The console exposes a tab for viewing logs for nodes. The journals tend to be extremely large. It appears that we are downloading the entire journal (hundreds of megs if my browser is to be believed) which then crashes the rendering and results in an empty journal being displayed in the log viewer. Another user reported that trying to view the node log in the browser crashed the entire browser (hard locked the tab).
How reproducible:
100%
Steps to Reproduce:
1. Compute -> Nodes -> Pick a node
2. View logs tab
3. Make sure journal is selected
Actual results:
Nothing is shown or browser crashes
Expected results:
Some journal lines should be shown
Additional info:
We might want to default to showing only the last 1000 lines or something
- clones
-
-
- Verified
-
- is blocked by
-
-
- Verified
-
- links to