Troubleshooting runtime issues

To diagnose problems, see the following information:

• Intermittent errors push images to Red Hat OpenShift integrated registry
• How do I use the local container registry provided with Red Hat OpenShift instead of a Docker Hub container registry?
• When using Red Hat OpenShift Container Platform on a cloud with Kubernetes service and an internal Docker registry, performing a docker push into the internal Docker registry might result in a gateway time-out error

Intermittent errors push images to Red Hat OpenShift integrated registry

You might receive one of the following messages:

• received unexpected HTTP status: 504 Gateway Time-out
• unable to retrieve auth token: invalid username/password

Performing a docker push to the Red Hat OpenShift integrated image registry can result in various intermittent errors. One cause for the errors can be the input/output operations per second (IOPS) setting of the backing storage of the integrated registry.

To resolve this problem, try the following:

1. Increase the IOPS setting of the PV backing storage device or increase the size of the backing storage.
2. Scale down the image registry deployment to 1 with the following command:

   oc -n openshift-image-registry scale deployment image-registry --replicas=1

How do I use the local container registry provided with Red Hat OpenShift instead of a Docker Hub container registry?

To use the local container registry provided with Red Hat OpenShift:

1. Find the local container registry URL given by Red Hat OpenShift in your cluster.
   1. In the Red Hat OpenShift web console, select the workspace default.
   2. Click the docker-registry pod.
   3. Click the Environment tab.
   4. Get the URL OPENSHIFT_DEFAULT_REGISTRY = docker-registry.default.svc:5000.
2. Once you have found the local container registry, use it while setting the webhook as value for the Docker Registry entry, or mention it when you are running the PipelineRun manually as a docker-image pipeline resource.
   • For example, in the pipelines dashboard via a webhook:

     Docker Registry : image-registry.openshift-image-registry.svc:5000/kabanero

   • For example, in a manual PipelineRun pipeline resource:

     docker-image : docker-registry.default.svc:5000/kabanero/my-image-name

When using Red Hat OpenShift Container Platform on a cloud with Kubernetes service and an internal Docker registry, performing a docker push into the internal Docker registry might result in a gateway time-out error

A gateway time-out error happens in cases where the input-output operations per second (IOPS) setting for the backing storage of the registry's persistent volume (PV) is too low.

To resolve this problem, change the IOPS setting of the PV's backing storage device:

docker-image : image-registry.openshift-image-registry.svc:5000/kabanero/my-image-name