Why does the Ingress status show an ERRIONF error?

Virtual Private Cloud Classic infrastructure Satellite

You can use the ibmcloud oc ingress status-report ignored-errors add command to add an error to the ignored-errors list. Ignored errors still appear in the output of the ibmcloud oc ingress status-report get command, but are ignored when calculating the overall Ingress Status.

When you check the status of your cluster's Ingress components by running the ibmcloud oc ingress status-report get command, you see an error similar to the following.

The Ingress Operator is missing from the cluster (ERRIONF).

The Ingress Operator is included in Red Hat OpenShift by default. An underlying cluster issue is causing the Operator to not deploy successfully.

Verify that the ingress ClusterOperator resource exists in your cluster.

1. Get the details of the ingress ClusterOperator.

   oc get clusteroperator ingress
   

   Example output

   NAME      VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
   ingress   4.10.22   True        False         False      45d
   

2. If the Operator exists and Progressing is True, wait 10 to 15 minutes to allow time for the Operator to finish deploying. If the operator doesn't exist, continue with the troubleshooting steps.

3. Follow the steps to review your cluster master and worker node states.

   • Review master health.
   • Review worker node states.

4. Refresh your cluster masters.

   ibmcloud oc cluster master refresh
   

5. After you refresh your cluster master, wait 10 to 15 minutes and then check the Ingress Operator status again by running the oc get clusteroperator ingress command. If the resource is still not created or is in a degraded state, contact support. Open a support case. In the case details, be sure to include any relevant log files, error messages, or command outputs.