Deploy Cloudera Manager with Rest Api template failed

biker — Wed, 20 Aug 2025 13:49:38 GMT

Hi,

we using the cdh_version: 7.1.9 and cm_version: 7.11.3

We want to deploy the cloudera manager with the json template file for our test automation. We want to use the rest API call "/cm/importClusterTemplate?addRepositories=true".
But we get the following error when we deploy the template json file.

{"message": "The following host(s) are not available: hdfs-11.vmlocal,hdfs-14.vmlocal,hdfs-12.vmlocal,hdfs-13.vmlocal."

The hdfs nodes are available and can be ping or ssh from the cloudera host.
The following packages are installed on each hdfs node:

cloudera-manager-daemons-7.11.3.7-52024171.el8.x86_64 cloudera-manager-agent-7.11.3.7-52024171.el8.x86_64 openjdk8-1.8.0_372_cloudera-1.x86_64

The cloudera-scm-agent running and the server_host entry in /etc/cloudera-scm-agent/config.ini points to the cloudera manager host (server_host=10.0.100.101)

We have read the cloudera documentation multiple times.

Does anyone has an idea why this error appears or how we can verify that the cloudera manager knows this hosts.
If we switch to the cloudera gui the hdfs nodes are find and it works.

Re: Deploy Cloudera Manager with Rest Api template failed

abdulpasithali — Wed, 20 Aug 2025 16:47:21 GMT

Hello @biker

Thank you for reaching out Cloudera Community.

We recommend you to check your cluster template parameters. For more details you shall refer the following documentations.

Dynamic cluster template parameters

Example Cluster Template

If everything is okay and the issue remains the same, kindly help us with more details such as complete error trace, screenshots etc.,

Re: Deploy Cloudera Manager with Rest Api template failed

biker — Thu, 21 Aug 2025 10:07:09 GMT

Hi Abdulpasithali,

thank you for looking at my post.

The template you point me is totally different to the template we are using.
I try to deploy the template and got empty brackets returned.

curl -X POST -H "Content-Type: application/json" -d @/tmp/cloudera_base_new.json http://admin:admin@9.152.187.116:7180/api/v54/cm/importClusterTemplate?addRepositories=true { }

You can find the template we using is to deploy a cloudera node here

Creating a Runtime Cluster Using a Cloudera Manager Template

We export the configuration from an existing Cloudera Cluster, changed some values at the json file and try to deploy it on a new cluster.
But this import failed.

curl -X POST -H "Content-Type: application/json" -d @/tmp/cloudera_base.json http://admin:admin@my_cloudera_ip:7180/api/v54/cm/importClusterTemplate?addReposiies=true { "message" : "The following host(s) are not available: hdfs-44.vmlocal,hdfs-42.vmlocal,hdfs-43.vmlocal,hdfs-41.vmlocal." }

Looking at the logfile at the cloudera node I see two java exceptions

2025-08-21 10:20:19,003 INFO scm-web-81:com.cloudera.server.web.cmf.AuthenticationSuccessEventListener: Authentication success for user: 'admin' from 9.152.187.253 2025-08-21 10:20:19,008 INFO scm-web-81:com.cloudera.enterprise.JavaMelodyFacade: Entering HTTP Operation: Method:POST, Path:/v54/cm/importClusterTemplate 2025-08-21 10:20:19,054 INFO scm-web-81:com.cloudera.enterprise.AbstractWrappedEntityManager: Rolling back transaction that wasn't marked for rollback-only. java.lang.Exception: Non-thrown exception for stack trace. at com.cloudera.enterprise.AbstractWrappedEntityManager.close(AbstractWrappedEntityManager.java:163) at com.cloudera.cmf.persist.CmfEntityManager.close(CmfEntityManager.java:408) at com.cloudera.server.web.cmf.AuthFilterEntityManager.close(AuthFilterEntityManager.java:202) at com.cloudera.api.dao.impl.ManagerDaoBase.runInNewTransaction(ManagerDaoBase.java:270) at com.cloudera.api.dao.impl.ManagerDaoBase.access$100(ManagerDaoBase.java:95) 2025-08-21 10:20:19,064 INFO scm-web-81:com.cloudera.api.ApiExceptionMapper: Exception caught in API invocation. Msg:The following host(s) are not available: hdfs-44.vmlocal,hdfs-42.vmlocal,hdfs-43.vmlocal,hdfs-41.vmlocal. java.lang.IllegalArgumentException: The following host(s) are not available: hdfs-44.vmlocal,hdfs-42.vmlocal,hdfs-43.vmlocal,hdfs-41.vmlocal. at com.google.common.base.Preconditions.checkArgument(Preconditions.java:143) at com.cloudera.api.dao.impl.ClouderaMasterServerDaoImpl.validateAndPrepareContext(ClouderaMasterServerDaoImpl.java:309) at com.cloudera.api.dao.impl.ClouderaMasterServerDaoImpl.importClusterTemplate(ClouderaMasterServerDaoImpl.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

The template we try to deploy looks like this

{ "cdhVersion":"7.1.9", "displayName":"storageScale", "cmVersion":"7.11.3", "repositories":[ "http://ip_address/repos/jenkins/BDA_CSTL/CDP7.1.9-CHF6/cdh-7.1.9.9/redhat8/" ], "products":[ { "product":"7.1.9-1.cdh7.1.9.p9.52289703-el8.parcel", "version":"CDH" } ], "services":[ { "refName":"spectrumscale", "serviceType":"SPECTRUMSCALE", "serviceConfigs":[ { "name":"default_fs_name", "value":"hdfs://cesnet-cluster-4.vmlocal:8020" }, { "name":"webhdfs_url", "value":"http://cesnet-cluster-4.vmlocal:50070/webhdfs/v1" } ], "roleConfigGroups":[ { "refName":"spectrumscale-TRANSPARENCY_DATANODE-BASE", "roleType":"TRANSPARENCY_DATANODE", "base":true }, { "refName":"spectrumscale-TRANSPARENCY_NAMENODE-BASE", "roleType":"TRANSPARENCY_NAMENODE", "base":true }, { "refName":"spectrumscale-GATEWAY-BASE", "roleType":"GATEWAY", "base":true } ] }, { "refName":"core_settings", "serviceType":"CORE_SETTINGS", "roleConfigGroups":[ { "refName":"core_settings-GATEWAY-BASE", "roleType":"GATEWAY", "base":true } ] } ], "hostTemplates":[ { "refName":"HostTemplate-0-from-hdfs-[43-44].vmlocal", "cardinality":"2", "roleConfigGroupsRefNames":[ "spectrumscale-GATEWAY-BASE", "spectrumscale-TRANSPARENCY_DATANODE-BASE" ] }, { "refName":"HostTemplate-1-from-hdfs-42.vmlocal", "cardinality":1, "roleConfigGroupsRefNames":[ "spectrumscale-GATEWAY-BASE", "spectrumscale-TRANSPARENCY_NAMENODE-BASE" ] }, { "refName":"HostTemplate-2-from-hdfs-41.vmlocal", "cardinality":1, "roleConfigGroupsRefNames":[ "core_settings-GATEWAY-BASE", "spectrumscale-GATEWAY-BASE", "spectrumscale-TRANSPARENCY_NAMENODE-BASE" ] } ], "tags":[ { "name":"_cldr_cluster.core_settings.service_name", "value":"core_settings" } ], "instantiator":{ "clusterName":"storageScale", "hosts":[ { "hostName":"hdfs-41.vmlocal", "hostTemplateRefName":"HostTemplate-2-from-hdfs-41.vmlocal" }, { "hostName":"hdfs-42.vmlocal", "hostTemplateRefName":"HostTemplate-1-from-hdfs-42.vmlocal" }, { "hostNameRange":"hdfs-[43-44].vmlocal", "hostTemplateRefName":"HostTemplate-0-from-hdfs-[43-44].vmlocal" } ], "lenient":false } }

Re: Deploy Cloudera Manager with Rest Api template failed

biker — Fri, 22 Aug 2025 07:07:28 GMT

@abdulpasithali
You may got notified on my last post. Because I forgot the @ on your name.
You may can read the post below.

Thanks

Re: Deploy Cloudera Manager with Rest Api template failed

jleandro-cr — Thu, 25 Sep 2025 02:41:26 GMT

Friendly reminder for you.

The recommendation is to use the hostname instead of the IP address for the server_host entry in the /etc/cloudera-scm-agent/config.ini file.

This allows more flexibility with DNS resolution and potential IP address changes.

question Re: Deploy Cloudera Manager with Rest Api template failed in Support Questions

Deploy Cloudera Manager with Rest Api template failed

Re: Deploy Cloudera Manager with Rest Api template failed

Re: Deploy Cloudera Manager with Rest Api template failed

Re: Deploy Cloudera Manager with Rest Api template failed

Re: Deploy Cloudera Manager with Rest Api template failed