IBM Cloud Docs
Why does the Ingress status show an ERRRNA error?

Why does the Ingress status show an ERRRNA 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 example.

One or more routes not admitted (ERRRNA).

The Ingress Controller watches Routes that are created on the cluster and marks them as admitted when the Ingress Controller configuration is adjusted. If a Route resource is not marked as admitted, it means that no Ingress Controllers has processed it, therefore the configuration is ineffective.

Review the configuration of Routes resources that have not been marked as admitted.

  1. Ensure that your cluster masters and workers are healthy.

  2. Fetch your Route resources and review their Status.

    oc get routes -A

  3. Identify Routes that do not look similar to the following contents in their Status field:

      status:
    ingress:
    - conditions:
      - status: "True"
        type: Admitted

  4. Review the configuration of Route resources that are not admitted:

    • Ensure the Route configuration is correct. See Route configuration.
    • Ensure you do not have two Route resources with the same host, in this case only one of them is admitted.
    • If you configured Ingress Controller sharding, ensure that the labels on the Route resource or on the namespace containing the Route resource are correct.

    If you no longer need the Route which is not admitted, delete it using the oc delete route command.

  5. Wait 10 to 15 minutes, then check your Routes again by running the oc get routes -A command.

  6. If you see a different error, repeat the troubleshooting steps. If the issue persists, contact support. Open a support case. In the case details, be sure to include any relevant log files, error messages, or command outputs.