---
name: openshift-ts-ingress-errrna
title: 'Ingress error: ERRRNA'
description: Learn how to resolve `ERRRNA` errors when one or more routes are not admitted by the Ingress Controller.
last-updated: 2026-07-10
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/openshift?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Ingress error: ERRRNA
{: #ts-ingress-errrna}
{: troubleshoot}
{: support}

[Virtual Private Cloud]{: tag-vpc} [Classic infrastructure]{: tag-classic-inf} [Satellite]{: tag-satellite}

Learn how to resolve `ERRRNA` errors when one or more routes are not admitted by the Ingress Controller.
{: shortdesc}

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.
{: tip}

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.
{: tsSymptoms}

```sh
One or more routes not admitted (ERRRNA).
```
{: screen}


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.
{: tsCauses}

Review the configuration of Routes resources that have not been marked as `admitted`.
{: tsResolve}

1. Ensure that your cluster masters and workers are healthy.
    - [Review master health](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_master&format=markdown#review-master-health).
    - [Review worker node states](https://cloud.ibm.com/docs/openshift?topic=openshift-worker-node-state-reference&format=markdown).

1. Fetch your Route resources and review their `Status`.
    ```sh
    oc get routes -A -o yaml
    ```
    {: pre}

1. Identify `Routes` that do not look similar to the following contents in their `Status` field:
    ```yaml
      status:
        ingress:
        - conditions:
          - status: "True"
            type: Admitted
    ```
    {: codeblock}

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

    - Ensure the Route configuration is correct. See [Route configuration](https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html/ingress_and_load_balancing/routes){: external}.
    - 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](https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html/networking_overview/index#nw-ingress-sharding_configuring-ingress){: external}, 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.
    {: tip}

1. Wait 10 to 15 minutes, then check your Routes again by running the `oc get routes -A` command.
1. If you see a different error, repeat the troubleshooting steps. If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/support?topic=support-using-avatar&format=markdown). In the case details, be sure to include any relevant log files, error messages, or command outputs.