Why does the Ingress status show an ERRESNF
error?
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.
The external service is missing (ERRESNF).
The service that exposes the default Ingress Controller is missing from the cluster.
Check the external service and create it if it doesn't exist.
-
Get the details of the external service.
oc get service -n openshift-ingress router-external-default
-
Get the external IP addresses of your worker nodes by running the following command. Make a note of the addresses in the
EXTERNAL-IP
column.kubectl get nodes -o wide
-
Save the following Service configuration as a YAML file called
service.yaml
.apiVersion: v1 kind: Service metadata: labels: ingresscontroller.operator.openshift.io/owning-ingresscontroller: default name: router-external-default namespace: openshift-ingress spec: ports: - name: http port: 80 protocol: TCP targetPort: http - name: https port: 443 protocol: TCP targetPort: https selector: ingresscontroller.operator.openshift.io/deployment-ingresscontroller: default externalIPs: - x.x.x.x # Add your worker node external IP addresses.
-
Add the external IP addresses of your worker nodes that you retrieved earlier in the
spec.externalIPs
list. -
Create the service.
kubectl create -f service.yaml
-
Wait 10 to 15 minutes, then check if the warning is resolved.
-
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.