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

metal3-ramdisk-logs busy loop burning a core away

XMLWordPrintable

    • None
    • 3
    • Metal Platform 266
    • 1
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

      clusters running on OpenShift Virt (Agent Based Install) where I see `metal3-ramdisk-logs` container eating up a core, but the logs are empty:
      oc adm top pod --sort-by=cpu --sum -n openshift-machine-api --containers 
POD                                           NAME                                     CPU(cores)   MEMORY(bytes)   
metal3-55c9bc8ff4-nh792                       metal3-ramdisk-logs                      988m         1Mi             
metal3-55c9bc8ff4-nh792                       metal3-httpd                             1m           20Mi            
metal3-55c9bc8ff4-nh792                       metal3-ironic                            0m           121Mi           
cluster-baremetal-operator-5bf8bcbbdd-jvhq7   cluster-baremetal-operator               1m           25Mi              

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

      4.17.12

      How reproducible:

      always

      Steps to Reproduce:

      Cluster is reachable on Red Hat VPN - reach out on slack to get access

      Actual results:

      logs are empty, but a core is consumed

      Expected results:

      container should be more or less idle

      Additional info:

              rpittau@redhat.com Riccardo Pittau
              dfroehli42rh Daniel Fröhlich
              Steeve Goveas Steeve Goveas
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: