dns-default service's IP already being allocated

Solution Verified - Updated -

Issue

  • The dns-default service fails to be created during cluster installation, as the IP requested for it has been already assigned to another service in the cluster.
  • The dns operator is not available and reports the following:
{
  "lastTransitionTime": "2022-11-24T03:57:14Z",
  "message": "DNS \"default\" reports Progressing=True: \"No IP address is assigned to the DNS service.\\nHave 0 available DNS pods, want 3.\"",
  "reason": "DNSReportsProgressingIsTrue",
  "status": "True",
  "type": "Progressing"
}

Environment

  • Red Hat OpenShift Container Platform [RHOCP]
    • 4.9
    • 4.10
    • 4.11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content