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

pods stuck in containercreating state.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • 4.12.0
    • 4.10.z
    • Node / CRI-O
    • None
    • Moderate
    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Pods are stuck on one of the nodes of the cluster and giving below error:
      ~~~
      Jan 03 05:27:32 hklvapapq750.dcda-dc1-prd2.ocp.sc.net hyperkube[3571]: E0103 05:27:32.784317    3571 pod_workers.go:951] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"ms-ccs-agent\" with CreateContainerError: \"Kubelet may be retrying requests that are timing out in CRI-O due to system load: context deadline exceeded: error reserving ctr name k8s_ms-ccs-agent_ms-ccs-agent-76ccb6576d-wgk82_api-banking_30db425f-c5a8-4867-a350-9c4578cb22ad_4 for id cddf2233764f814833e691820903408bb59f3ad1e4e3e00a2fda1dd33cf0bba1: name is reserved\"" pod="api-banking/ms-ccs-agent-76ccb6576d-wgk82" podUID=30db425f-c5a8-4867-a350-9c4578cb22ad
      Jan 03 05:27:33 hklvapapq750.dcda-dc1-prd2.ocp.sc.net hyperkube[3571]: I0103 05:27:33.465943    3571 scope.go:110] "RemoveContainer" containerID="616dc7954d0038c65e9be0847046cd8be983dfdb651c45e80ba95a8af2d7ab5e" 
      ~~~
      Checked on node CPU and Memory load was under threshold. 
       

      How reproducible:

       

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

       

      Expected results:

       

      Additional info:

       

              pehunt@redhat.com Peter Hunt
              rhn-support-tkondvil Tejas Kondvilkar
              Anurag Saxena Anurag Saxena
              Tejas Kondvilkar
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: