IBM Cloud Docs
Why does my Private Path NLB contain a hostname.invalid error?

Why does my Private Path NLB contain a hostname.invalid error?

When describing your LoadBalancer by using the oc describe svc SERVICENAME -n NAMESPACE command, you see an error message similar to the following.

Error on cloud load balancer prod-sat1-ppnlb for service openshift-ingress/router-default-ppnlb with UID c89cde55-777f-4d99-aacf-09108d90fa9c: Service and associated VPC load balancer do not match: Service external IPs:, VPC load balancer IPs:XX.XX.XX.XX,XX.XX.XX.XX,XX.XX.XX.XX,XX.XX.XX.XX

You also see the LoadBalancer Ingress field contains hostname.invalid.

LoadBalancer Ingress: hostname.invalid

The issue is caused by a mismatch between the Kubernetes service configuration and the LoadBalancer. This is a known issue in versions prior to 4.16.40_1567_openshift. The affected PPNLB was created before the rollout of the fix included in 4.16.40_1567_openshift.

Recreate your PPNLB to resolve the issue.

  1. Delete all associated resources linked to the service.
  2. Delete and recreate the PPNLB service.
  3. Verify that hostname.invalid no longer appears in the LoadBalancer Ingress field and that no warnings are present in the Events section when you describe the service.
  4. 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.