Hide Forgot
Created attachment 1212209 [details] Screenshot after memory graph failure Description of problem: On the metrics tab for a pod, change the time range to "Last Week" . Immediately change the time range back to "Last Hour" . The memory graph will no longer render. Version-Release number of selected component (if applicable): 3.3 Firefox 47 How reproducible: 100% Steps to Reproduce: 1. Create a pod 2. Navigate to view the Metrics tab in the pod's details 3. Change time range to "1 week" 4. Change time range back to "1 hour" Actual results: The memory graph will no longer render. Expected results: The memory graph should recover as the CPU/Network do. Additional info:
Checked on OCP 3.3.1.3, this bug can be reproduced most of the time. Change the time range to "Last Week", or "Last 3 days", "Last day", then change time range to "Last hour", the metrics charts for memory, cpu and network are all not recovered. Sometimes they are recovered, reproduction rate is different for different pod. Pls refer to attachment.
Created attachment 1212470 [details] after-change
Created attachment 1212471 [details] before-change
Looking at all three screenshots, I believe this is the y-axis scale issue in all cases. (Current and recent usage values are too large to display with the current y-axis scale.) *** This bug has been marked as a duplicate of bug 1386823 ***