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

Why does the Ingress status show an ERRDSIA error?

Virtual Private Cloud Classic infrastructure Satellite

You can use the ibmcloud ks 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 ks 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 ks ingress status-report get command, you see an error similar to the following example.

The subdomain has incorrect addresses registered (ERRDSIA).

Normally, the NLB-DNS subdomains should hold IP addresses or load balancer hostnames that are tied to one or more LoadBalancer services on your cluster, but one or more domains have unknown addresses registered.

Identify and update any NLB-DNS subdomains that have incorrect addresses registered.

  1. Get the list of the managed domains using the ibmcloud ks ingress domain ls command.

  2. Get the list of LoadBalancer services from your cluster.

    kubectl get services -A | grep LoadBalancer

  3. Compare the outputs of the two previous commands and identify the subdomains that have incorrect addresses registered.

  4. If you no longer need a specific domain, you can use the ibmcloud ks ingress domain rm command to remove it.

  5. If you still need the domain, you can update the registered addresses for the domain by using the ibmcloud ks ingress domain update command command.

    Note that you must include all addresses you want to be registered as the update operation replaces the currently registered addresses. For example, if 52.137.182.166 is currently registered to your domain and you want to add 52.137.182.270, you must specify --ip 52.137.182.166 --ip 52.137.182.270 in the command.

  6. Wait a 15-30 minutes, then check if the warning is resolved.

  7. 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.