Help Center/ DataArts Studio/ FAQs/ DataArts Migration (CDM Jobs)/ What Should I Do If a CDM Cluster Fails to Be Created?
Updated on 2026-09-01 GMT+08:00
View PDF
Share

What Should I Do If a CDM Cluster Fails to Be Created?

The following table lists the common causes of CDM creation failures and solutions.

Table 1 Common failure causes and solutions

Error Code

Error Message

Description

Solution

Ecs.0001
  • the added number of cpu [2] above left profit [0].
  • the added size of ram [8192] above left profit [0].

Insufficient quota
  • Release idle resources, for example, delete unnecessary CDM clusters. For details about how to delete a cluster, see Deleting a CDM Cluster.
  • Contact customer service or technical support.

Ecs.0021

Failed to check Cinder quotas because the number of Gigabytes exceeded the upper limit.

Ecs.0204

FSOPS.NOVA.NoValidHost!

Insufficient resources

Ecs.0018

Flavor xxx is sold out.

Insufficient resources
  • Create a CDM cluster again and select another AZ or flavor. For details about how to create a cluster, see Creating a CDM Cluster.
  • Contact customer service or technical support.

Ecs.0005

imageRef should not be null or empty.

Deployment issue

Contact customer service or technical support.

Ecs.0319

The capacity of flavor xxx is not sufficient.

Insufficient resources

CDM.6016

[RdsPingInstanceManagerlPtask][onListenFailedAfterExecute]Connect

instance SSH service failed,listen times out!

instanceId:[xxx],managerIp:[xx.xx.xx.xx]

connect instance SSH service failed,for the

network is unreachable.

The attempt of the management node (managerIp) to connect to the data node through SSH times out due to network disconnection.