Image pull from internal registry failing with "500 Internal server Error" in RHOCP4

Solution Verified - Updated -

Issue

  • Pod failing with ImagePullBackOff when deployment configured with internal image url. Same deployment is working fine when upstream registry url is used.
Back-off pulling image "image-registry.openshift-image-registry.svc:5000/<repo>/<image>:<tag>"
  • Manual image pull failing with below error:
error: initializing source docker://image-registry. openshift-image-registry.svc: 5000/<repo>/<image>:<tag>: reading manifest <tag> in image-registry.openshift-image-registry.svc:5000/<repo>/<image>:<tag>: received unexpected HTTP status: 500 Internal server Error
  • Observed below error in image-registry pod:
level=error msg="response completed with error" err.code=unknown err.detail="unexpected end of JSON input" err.message="unknown error"

Environment

  • Red Hat Openshift Container Platform (RHOCP) 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content