Why does the Ingress status show an ESSSMINF error?
Virtual Private Cloud Classic infrastructure
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 example.
The Secrets Manager instance is not found (ESSSMINF).
The Kubernetes Service is unable to access the Secrets Manager instance. The instance might have been deleted from your IBM Cloud account, but still remains registered to your cluster.
Check that the Secrets Manager instances registered to your cluster still exist in your IBM Cloud account.
- List the Secrets Manager instances that are registered to your cluster.
ibmcloud oc ingress instance ls --cluster <cluster> - List the resources in your account and check that the Secrets Manager instances registered to your cluster also exist in your account.
ibmcloud resource service-instances - If the Secrets Manager instance no longer exists in your account, remove it from the cluster.
ibmcloud oc ingress instance unregister - If the problem persists, [open a support ticket](/docs/openshift?topic=openshift-get-help.