Ingress error: ERRAHSNF

Virtual Private Cloud Classic infrastructure

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.

One or more ALB health service is not found on the cluster (ERRAHSNF).

IBM Cloud Kubernetes Service deploys managed health check services to every cluster. If one or more service is missing from your cluster, this might result in invalid health check results.

Trigger a reconcile on the health ingresses.

1. Run the following command either for all ALBs or target at least one enabled ALB.

   ibmcloud ks ingress alb update --cluster CLUSTER [--alb ALB ...] [--output OUTPUT] [-q] [--version VERSION]
   

2. Wait 10-15 minutes, then retry the ibmcloud ks ingress status-report get command to see if the issue is resolved.

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