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

Rollout of image-registry pod is not happening and pods are going into ContainerCreating

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • 4.12
    • Image Registry
    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Hi Team, IHAC who is running 4.12.50 OCP cluster. On their cluster replica of image registry pod is getting increasing automatically.

      image-registry-56d99c584c-6thfs                    1/1     Running                0          88d   10.131.24.77   o-intworker-5.omega.xcv.net        <none>           <none>
      image-registry-7478d88b65-b9t25                    0/1     ContainerCreating      0          54m   10.131.25.44   o-intworker-5.omega.xcv.net        <none>           <none>
      

      The new replica count pod is in  CreateContainerError with below error:

      50m         Warning   Failed                   pod/image-registry-56d99c584c-5v7mv          Error: kubelet may be retrying requests that are timing out in CRI-O due to system load. Currently at stage container volume configuration: context deadline exceeded: error reserving ctr name k8s_registry_image-registry-56d99c584c-5v7mv_openshift-image-registry_fdf6c90c-507f-4aab-aa60-12dd091cc605_0 for id e026b4f08f5cab88661c160c8731355ceea26baa42a0ad7df4330eb295f5ad98: name is reserved
      

      In `oc get configs.imageregistry.operator.openshift.io i have checked and found that replica count are mentioned as only 1, but still I could see two image-registry pod and sometime more.

      Looks like rollout of image-registry rs is not happening properly that's why the new pod of image-registry is getting created and stuck on CreateContainerError with error name is reserved and old revision pod is running fine.

      image-registry-56d99c584c-2wzlj 0/1 CreateContainerError 0 1h
      image-registry-6c5c45776-6lkqf 1/1 Running 0 1h 

      We have tried to rollback the revision but it also did not help.

       $ oc rollout undo deploy image-registry -n openshift-image-registry

       

      Can some one please help me to know why these rollout is failing? and how can be fix it?

      Version-Release number of selected component (if applicable):
      {code:none} 4.12.40
          

      How reproducible:

          

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

      rollout of image-registry is not happening

      Expected results:

          rollout of images-registry should happen

      Additional info:

         slack discussion https://redhat-internal.slack.com/archives/C013VBYBJQH/p1716481738611149 

       

              fmissi Flavian Missi
              rhn-support-psingour Poornima Singour
              XiuJuan Wang XiuJuan Wang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: