Cloudera Altus Cluster Creation fails with INTERNAL_CM_CMD_FAIL on AWS

by Cloudera Employee Anthony ‎04-09-2018 10:03 AM - edited ‎06-26-2018 08:31 AM

Symptoms

When attempting to create a Cloudera Altus cluster in AWS, it fails with INTERNAL_CM_CMD_FAIL

Diagnosis

  • CM Deployment is failing at the creation / deployment of CM services due to incorrect or unexpected DNS hostnames of the AWS EC2 instances created for Cloudera Altus.
  • Cloudera Altus requires the options DNS hostnames and DNS resolution are enabled (set to yes) within the AWS VPC settings

Solution

  1. Set and confirm DNS hostnames and DNS resolution are set to yes in the AWS VPC used for Cloudera Altus.
    Details for configuring AWS VPCs with DNS is available here:
    https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-dns.html
  2. Once the AWS VPC DNS settings of the Cloudera Altus Environment are enabled, ensure to delete the previous cluster creation attempt's EC2 instances, both within a Cloudera Altus console, as well as through the AWS EC2 interface
  3. Retry creating a new Cloudera Altus cluster with the updated settings
Comments
by kostasm
on ‎07-18-2018 07:40 AM

Hello Anthony,

 

I face the same issue but I am trying to create a cluster on Azure. 

What is the corresponding for Azure solution?

 

Thanks and best regards,

kostasm

 

by Cloudera Employee Tony Wu
on ‎07-18-2018 07:46 AM

Hi @kostasm,

 

Please check and confirm you have created the VNET and DNS server with the Altus ARM template for your Altus environment. If so please also check in Azure portal to make sure the DNS server VM created by the Altus ARM template is up and running.

 

Thanks,

Tony

by kostasm
on ‎07-19-2018 12:40 AM

Hi Tony,

 

I have provisioned the "Cloudera Altus Service Image 5.14" from Azure portal. All the default services are running (e.g VNET, NSG, DNS). The DNS is inherited from virtual network.

 

Thanks,

Kostas