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

[4.10] cri-o should report the stage of container and pod creation it's stuck at

XMLWordPrintable

    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      in situations of load, cri-o reports `name is reserved` errors to the kube API when kubelet re-requests a pod or container that cri-o is taking a long time creating. inside of those errors, cri-o should report the stage of the creation the resource is, so the user has insight into where it's stuck
      

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

      all

      How reproducible:

      100%

      Steps to Reproduce:

      1. cause a container creation to take a long time
      2. note the stage the container creation is stuck at in cri-o logs
      3.
      

      Actual results:

      no stage reported

      Expected results:

      stage reported

      Additional info:

       

            pehunt@redhat.com Peter Hunt
            pehunt@redhat.com Peter Hunt
            Min Li Min Li
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: