Skip to main content
Question

IFS pods stuck in ImagePullBackOff Status

  • October 3, 2022
  • 1 reply
  • 490 views

Forum|alt.badge.img+6

Hi,

This is new installation for IFS Cloud 22R1 and four of pods are stuck in ImagePullBackOff Status.

I have tried deleting all Pod replicas belonging to the deployments in error but still i am getting same error.

Any idea what can be the reason for error.

 

 

Describe pod gives below given error. This is for ifsapp-iam pod:

Warning  Failed       14m                   kubelet            Failed to pull image "ifscloud.jfrog.io/docker/ifs/ifsapp-iam:22.1.3.0.0": rpc error: code = NotFound desc = failed to pull and unpack image "ifscloud.jfrog.io/docker/ifs/ifsapp-iam:22.1.3.0.0": failed to copy: httpReadSeeker: failed open: could not fetch content descriptor sha256:4e764e449e2e20a118dd9425e79b0f983dba7d479fb668af3497b0c1665bace3 (application/vnd.docker.image.rootfs.diff.tar.gzip) from remote: not found
  Warning  Failed       13m (x4 over 14m)     kubelet            Error: ImagePullBackOff
  Normal   Pulling      13m (x3 over 14m)     kubelet            Pulling image "ifscloud.jfrog.io/docker/ifs/ifsapp-iam:22.1.3.0.0"
  Warning  Failed       13m (x2 over 13m)     kubelet            Failed to pull image "ifscloud.jfrog.io/docker/ifs/ifsapp-iam:22.1.3.0.0": rpc error: code = NotFound desc = failed to pull and unpack image "ifscloud.jfrog.io/docker/ifs/ifsapp-iam:22.1.3.0.0": failed to copy: httpReadSeeker: failed open: could not fetch content descriptor sha256:59172b340b0dfe36fc628b406bf2200268365ac0d525e39c067c246955c722c5 (application/vnd.docker.image.rootfs.diff.tar.gzip) from remote: not found
  Warning  Failed       13m (x3 over 14m)     kubelet            Error: ErrImagePull
  Normal   BackOff      4m18s (x40 over 14m)  kubelet            Back-off pulling image "ifscloud.jfrog.io/docker/ifs/ifsapp-iam:22.1.3.0.0"

Forum|alt.badge.img+6
  • Do Gooder (Partner)
  • October 3, 2022

Even if i restart the machine or reinstall middle-tier using installer.cmd then also issue is only coming for these 4 pods only. It seems to be some issue with the repository itself.

Not sure if someone can help me in checking the repository.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings