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

Why does the Ingress status show an ERRSAM error?

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.

The load balancer service address is missing (ERRSAM).

The load balancer service that exposes your ALB doesn't have an address assigned.

Complete the following steps to troubleshoot the issue.

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

  2. List your load balancer services.

    kubectl get services -n kube-system | grep LoadBalancer

  3. Identify services that do not have an address in the EXTERNAL-IP column.

  4. Look for an event that references the following services.

    kubectl get events -n kube-system | grep SERVICE

  5. Review contents of the MESSAGE column and complete the following steps based on your cluster type and error message.

    • If you see errors regarding your API key, you can try resetting the API key with the ibmcloud ks api-key reset command.
    • Classic: If you see errors regarding your load balancer deployment, ensure your cluster has at least two healthy workers. For more information, see Adding worker nodes and zones to clusters.
    • Classic: If you see errors saying that the IP of the ALB is not available, disable the ALB using the ibmcloud ks ingress alb disable command, then reenable it with the ibmcloud ks ingress alb enable classic command and specify the --ip flag with a free IP address from the error message.
    • Classic: If you see errors saying that no IPs are available, add new portable subnets to the cluster with the ibmcloud ks cluster subnet create command.
    • VPC: If you see permission issues, review your IAM permissions. For more information, see Setting up an Application Load Balancer for VPC.
    • VPC: Ensure that you did not reach your LBaaS instance quota. For more information, see Quotas and service limits and ibmcloud is load-balancers command.

  6. Wait 10 to 15 minutes, then check if the load balancer got an address assigned. If not, check the events again.

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