question Failure to Install Embedded Container Service (ECS), encountering "Error while getting account id. dial tcp: lookup cloud data service console on ip:53: no such host" in Support Questions

Failure to Install Embedded Container Service (ECS), encountering "Error while getting account id. dial tcp: lookup cloud data service console on ip:53: no such host"

steinsgate — Tue, 21 Apr 2026 06:32:46 GMT

Hi everyone, I would like some clarification. Thank you.

We are encountering a blockage during the installation of the Embedded Container Service (ECS).

Encountering the following error:

2024/04/03 17:29:48 kubectl get secret cm.creds -n cdp 2024/04/03 17:39:38 Error while getting account id. Get "https://console-cdp.apps.ecsm0.am.ocp.poc/authenticate/login": dial tcp: lookup console-cdp.apps.ecsm0.am.ocp.poc on 192.168.30.206:53: no such host 2024/04/03 17:39:38 Retry GetAccountId after 10 seconds... 2024/04/03 17:39:48 There is an error while retrieving the account id. panic: There is an error while retrieving the account id. goroutine 1 [running]: log.Panicf({0x176705e?, 0xc00074c4c0?}, {0x0?, 0xc00074c4c0?, 0xc00074c4ea?}) /grid/0/jenkins/workspace/workspace/App_builds/SOURCES/cdp-private/thirdparty/go/src/log/log.go:391 +0x67 main.GetAccountId({0xc00074c4c0, 0x3c}) /grid/0/jenkins/workspace/workspace/App_builds/SOURCES/cdp-private/src/go/create-cm-cred.go:129 +0x1ef main.(*CdpInstaller).CreateCmCred(0xc000605e28?) /grid/0/jenkins/workspace/workspace/App_builds/SOURCES/cdp-private/src/go/create-cm-cred.go:51 +0x14a main.(*CdpInstaller).installControlPlane(0xc000605e28) /grid/0/jenkins/workspace/workspace/App_builds/SOURCES/cdp-private/src/go/helm-install-all.go:570 +0x36b main.main() /grid/0/jenkins/workspace/workspace/App_builds/SOURCES/cdp-private/src/go/main.go:26 +0xde 2024/04/03 17:39:48 ========================================================================================= 2024/04/03 17:39:48 Report workflow status: 2024/04/03 17:39:48 { "WorkflowStatusArray": null, "AllFlowsSucceeded": false

Do we need to configure anything for DNS for Embedded Container Service (ECS)? Or do we need to configure anything in k8s pods?

Re: Failure to Install Embedded Container Service (ECS), encountering "Error while getting account id. dial tcp: lookup cloud data service console on ip:53: no such host"

upadhyayk04 — Wed, 03 Apr 2024 10:54:30 GMT

Hello @steinsgate

Thank you for raising this

This looks to be a DNS issue on the host, Have you configured the DNS as per the below on the host

The cluster generates multiple hosts and host based routing is used in the cluster in order to route it to the right service. You must decide on a domain for the services which Cloudera Manager by default points to one of the host names on the cluster. However, during the installation, you should check the default domain and override the default domain (only if necessary) with what you plan to use as the domain. The default domain must have a wildcard DNS entry. For example, “*.apps.myhostname.com”. It is recommended that you leave IPv6 enabled at the OS level on all ECS nodes.

https://docs.cloudera.com/cdp-private-cloud-data-services/1.5.3/installation-ecs/topics/cdppvc-installation-ecs-software-requirements.html

Can you please re-check if the pre-reqs have been set up correctly.

2024/04/03 17:39:38 Error while getting account id. Get "https://console-cdp.apps.ecsm0.am.ocp.poc/authenticate/login": dial tcp: lookup console-cdp.apps.ecsm0.am.ocp.poc on 192.168.30.206:53: no such host

Re: Failure to Install Embedded Container Service (ECS), encountering "Error while getting account id. dial tcp: lookup cloud data service console on ip:53: no such host"

steinsgate — Wed, 03 Apr 2024 18:27:29 GMT

Hello @upadhyayk04

I would like some clarification. Thank you.

I found this warning, I don’t know if it’s the reason.

Re: Failure to Install Embedded Container Service (ECS), encountering "Error while getting account id. dial tcp: lookup cloud data service console on ip:53: no such host"

upadhyayk04 — Thu, 04 Apr 2024 00:55:53 GMT

Hello @steinsgate

Thank you for your update

Yes please ensure that the DNS configuration is correct on the nodes. I mean to say that it should adhere to our documentation.

Also, try resolving the hostname manually using nslookup from the nodes and compare the output from the working nodes and see if that works