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

Pod fails to start due to CRI-O load with OnRootMismatch implemented

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Normal Normal
    • None
    • 4.10.0
    • Node / CRI-O
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • None
    • None
    • Rejected
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Pods failing to start with the error:
      err="failed to \"StartContainer\" for \"odmrulepromotion\" with CreateContainerError: \"Kubelet may be retrying requests that are timing out in CRI-O due to system load: the requested container k8s_odmrulepromotion_odmrulepromotion-prod-27740683-c9sm6_rma-apps_971dbe9b-d7c4-4c80-a3be-870db9c061ff_0 is now ready and will be provided to the kubelet on next retry: error reserving ctr

      They upgraded the cluster to 4.10 and added the OnRootMismatch annotation but are still encountering the above CRI-O load errors.

      The PV is an OCS/ODF backed pv with about ~76k files

              pehunt@redhat.com Peter Hunt
              rhn-support-dseals Daniel Seals
              Sunil Choudhary Sunil Choudhary
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: