General Page
A common issue with OCP environments is an error known as "PR_END_OF_FILE_ERROR". Normally the cluster operators can be checked and there will be an error on the ingress operator. These steps will restart the ingress pods.
- Download kubeconfig from reservation
- Open terminal or other command prompt interface
- Navigate to the location of the kubeconfig file
- Run "export KUBECONFIG=conf_kubeconfig_download.conf" (This points you to the cluster of the reservation)
- Run "oc get co"
This will gather the cluster operators and any errors/ statuses/ degradations. If OC CLI is not installed, follow instructions here: https://docs.openshift.com/container-platform/4.8/cli_reference/openshift_cli/getting-started-cli.html - Run "oc delete po --all -n openshift-ingress"
Restarts ingress pods - Run "oc get po -n openshift-ingress"
Checks status of ingress pods. Once both are running, cluster should be accessible
Additionally, if any nodes have been added, make sure that the number of ingress replicas matches the number of worker nodes.
oc patch -n openshift-ingress-operator ingresscontroller/default --patch '{"spec":{"replicas": 10}}' --type=merge
[{"Type":"MASTER","Line of Business":{"code":"","label":""},"Business Unit":{"code":"","label":""},"Product":{"code":"SSNR6KN","label":"IBM Technology Zone"},"ARM Category":[{"code":"a8mKe0000004CUcIAM","label":"Infrastructure-\u003EVMWare"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
02 October 2025
UID
ibm17184687