Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-14656

With OpenShift Web Console Dashboards in 4.12, memory limits and requests are not overlayed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • None
    • 4.12.z
    • Observability UI
    • None
    • Moderate
    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      From Openshift 4.12 Webconsole Administrator->Observe->Dashboards, both CPU and Memory Usage graphs display values for available containers CPU/Memory usage cumulatively. These values should instead be overlayed. 
      
      When clicking the `Inspect` option of the CPU/Memory Usage panel, the values are showed overlayed and not cumulatively. 
      
      When we move the mouse over the CPU/Memory Usage graph, there is pop-up dialog that displays CPU/Memory limit & resource values, however, the Y-axis values display the total value equal to the sums of the available containers(i.e. container1 usage + container2 usage + ...). 

      Version-Release number of selected component (if applicable):

      OCP 4.12

      How reproducible:

      all the time

      Steps to Reproduce:

      1. install OCP 4.12
      2. Check Y-axis values for CPU Usage & Memory Usage graphs available from Administrator Webconsole-->Observe-->Dashboards
      

      Actual results:
      The pop-up dialog that occurs in CPU Usage & Memory Usage panel displays correct resource usage values. Values seen in Y-axis, however, shows the total value that sums individual containers values(i.e. container1 usage +. container2 usage)
      Expected results:

      The pop-up dialog that occurs in CPU Usage & Memory Usage panel displays correct resource usage values. Thus, the values seen in Y-axis should also be overlayed. 

      Additional info:

       

            gbernal@redhat.com Gabriel Bernal
            rhn-support-vchalise Vibhuti Chalise
            Junqi Zhao Junqi Zhao
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: