Uploaded image for project: 'Data Foundation Bugs'
  1. Data Foundation Bugs
  2. DFBUGS-372

[2266599] [IBM Z] - Noobaa pod idle cpu consumption is higher that expected value 0.1

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • odf-4.15
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • If docs needed, set a value
    • None

      Description of problem (please be detailed as possible and provide log
      snippets):

      Nooba pods CPU usage on idle cluster is observerved to be higher that expected value 0.1.
      Identified via ocs-ci test : tests/functional/monitoring/prometheus/metrics/test_ocs_utilization.py::test_mcg_cpu_usage

      Version of all relevant components (if applicable):
      ODF: v4.15.0-149
      OCP: 4.15.0-rc.7

      Does this issue impact your ability to continue to work with the product
      (please explain in detail what is the user impact)?

      Is there any workaround available to the best of your knowledge?

      Rate from 1 - 5 the complexity of the scenario you performed that caused this
      bug (1 - very simple, 5 - very complex)?

      Can this issue reproducible?
      yes

      Can this issue reproduce from the UI?
      yes, check noobaa pod CPU usage on an idle cluster

      If this is a regression, please provide more details to justify this:

      Steps to Reproduce:
      1. Deploy OCP followed by ODF
      2. Observer nooba pod consumption from monitoring dashboard
      3.

      Actual results:

      Expected results:

      Additional info:
      ocs-ci logs and must-gather available in google drive: https://drive.google.com/file/d/1YD29QMvlOGbHKThwqV7HPXnR08Nf73Hm/view?usp=sharing

              rh-ee-nbecker Nimrod Becker
              akandath Abdul Rauf Kuyyil Kandathil
              Krishnaram Karthick Ramdoss Krishnaram Karthick Ramdoss
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: