Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

CDP data lake failing with Provisioning Failed. (But it provisioned hardware)

avatar
New Contributor

There events error is: "Operation timed out. Template install timed out with this command id: 1546332222"

Here's the complete sequence of events:

 

 

 

Operation timed out. Template install timed out with this command id: 1546332222
4/28/2020, 2:10:09 PM
Building cluster; Cluster manager ip:xxx.xxx.xxx.xxx
4/28/2020, 1:21:37 PM
Retrying Create cluster operation from the failed step.
4/28/2020, 1:21:37 PM
Cloudera Manager reported that node(s) data-lake-eastern-us-master0.dev-test.udum-f5f2.cloudera.site,data-lake-eastern-us-idbroker1.dev-test.udum-f5f2.cloudera.site status became HEALTHY.
4/28/2020, 1:12:44 PM
Operation timed out. Template install timed out with this command id: 1546332222
4/28/2020, 1:12:19 PM
Building cluster; Cluster manager ip:xxx.xxx.xxx.xxx
4/28/2020, 12:23:36 PM
Starting cluster services
4/28/2020, 12:21:14 PM
Starting cluster services
4/28/2020, 12:19:14 PM
Setting up infrastructure metadata
4/28/2020, 12:17:34 PM
Bootstrapping infrastructure cluster
4/28/2020, 12:17:09 PM
Registering proxy configuration with Cluster Proxy
4/28/2020, 12:17:09 PM
Infrastructure successfully provisioned
4/28/2020, 12:17:09 PM
Infrastructure metadata collection finished
4/28/2020, 12:16:32 PM
Infrastructure creation took 79 seconds
4/28/2020, 12:16:31 PM
Creating infrastructure
4/28/2020, 12:15:11 PM
Setting up CDP image
4/28/2020, 12:15:11 PM

 

 

 Seems odd that it times out after 50 minutes when the documentation says it can take an hour to provision.... Any way I can increase the timeout?

Retry failed, and I can't repair because the nodes are up and reporting healthy....  Any thoughts on what I can look into to get more information into this post I'd appreciate the help.

1 ACCEPTED SOLUTION

avatar
New Contributor

For those that read this.  I think the issue was actually related to an amazon account issue.  Apparently when you have a brand new account they don't let you provision right away.  I spontaneously got an email from Amazon saying they had fixed things, and I know longer get this error.  I have no idea what they fixed:

Dear AWS Customer,

Thank you for using Amazon Web Services!

You recently requested an AWS Service that required additional validation. Your request has now been validated for AWS US East (Ohio) region(s). If you are still experiencing difficulty, please contact us at aws-verification@amazon.com.

Thank you for your patience. 

—The Amazon Web Services Team

If other encounter this issue, I guess you need to wait until amazon sees what you are doing and 'fixes' it.

View solution in original post

1 REPLY 1

avatar
New Contributor

For those that read this.  I think the issue was actually related to an amazon account issue.  Apparently when you have a brand new account they don't let you provision right away.  I spontaneously got an email from Amazon saying they had fixed things, and I know longer get this error.  I have no idea what they fixed:

Dear AWS Customer,

Thank you for using Amazon Web Services!

You recently requested an AWS Service that required additional validation. Your request has now been validated for AWS US East (Ohio) region(s). If you are still experiencing difficulty, please contact us at aws-verification@amazon.com.

Thank you for your patience. 

—The Amazon Web Services Team

If other encounter this issue, I guess you need to wait until amazon sees what you are doing and 'fixes' it.