- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Template error creating HDP-Cloud Controller Service on AWS
- Labels:
-
Hortonworks Data Platform (HDP)
Created ‎01-25-2017 03:00 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please see the attached two documents for details:
Document 1: Create Failed-Stack Detail.pdf... contains the error details
Document 2: Create Failed-Procedure-I-Used.pdf ... contains the procedure I followed.
Please advise on how to move forward as I have not been able to create a cluster using the new HDP Cloud on AWS.
Regards
Joginder
Created ‎01-25-2017 10:12 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One last thing that comes to my mind: Did you use any special characters in your password? At some point, we had problem with some special characters in the Admin Password parameter.
The log says time="2017-01-25T21:20:51Z" level="error" msg="[NewOAuth2HTTPClient] Error while connnecting to https://ec2-52-90-192-197.compute-1.amazonaws.com/identity/oauth/authorize as user: at46@yahoo.com, please check your username and password. (406 Not Acceptable)"
Created ‎01-25-2017 03:21 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Marton Sereg Do you know why this error happens? The error is:
CREATE_FAILED
AWS::CloudFormation::WaitCondition InstanceWaitCondition
WaitCondition received failed message: 'ERROR: command 'hdc createÂcredential ÂÂ credentialÂname awsÂaccess ÂÂroleÂarn $CREDENTIAL_ROLE_ARN ÂÂsshÂkeyÂurl http://169.254.169.254/latest/metaÂdata/publicÂkeys/0/opensshÂkey ÂÂexistingÂsshÂkeyÂpair $KEYPAIR_NAME' exited with status: 1 line: 1' for uniqueId: cbdÂinit
We don't have it documented in the Troubleshooting documentation at http://hortonworks.github.io/hdp-aws/trouble/index.html
Created ‎01-25-2017 03:35 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't know why this error occurred: I am seeking advise on resolving it. Can you please help?
Created ‎01-25-2017 10:13 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
can you SSH to the control plane VM and send me the logs from:
- /var/log/cbd-quick-start.log
- the output of the "docker logs cbreak_cloudbreak_1" command
I've seen this error message once when the SSH public key that was selected on the CFN create stack page had a length shorter than 2048. Please check if your public key's length is at least 2048 because only those are supported by HDC.
Created ‎01-25-2017 07:42 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am unable to Putty into the vpc. The .pem file is 2kb while when I generate .ppk files: the private key is 2kb but the public key is 1kb. When generate another pair of keys using AWS' "Create Key Pair" I don'r see an option to set the size of the keys.
Please advise.
Regards @Marton Sereg
Joginder
Created ‎01-25-2017 07:39 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am unable to Putty into the vpc. The .pem file is 2kb while when I generate .ppk files: the private key is 2kb but the public key is 1kb. When generate another pair of keys using AWS' "Create Key Pair" I don'r see an option to set the size of the keys.
Please advise.
Regards @Marton Sereg
Joginder
Created ‎01-25-2017 07:54 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What Marton meant is, SSH to the EC2 instance on which the cloud controller is running, and get the output of the logs.
To determine your SSH public key length, you could use this command ssh-keygen -lf /etc/ssh/rsa_key.pub replacing rsa_key.pub with your public key name.
If you have already generated a new kaypair, you could just try and create a new cloud controller using the new SSH keypair.
By the way, if you run into any further issues, let us know which version of HDCloud you are using. I assume 1.8? Or the technical preview?
Created ‎01-25-2017 08:07 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am using 1.8 version of HDCloud. I have terminated ec2 instance base on your recommendation to try with newly generated key pairs.
Will report soon.
Regards @Dominika Bialek
Created ‎01-25-2017 08:09 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Great. Let us know how it goes. If you generated a new SSH key, it should be a 2048-bit RSA key that meets the requirements. If the cloud controller still fails, then something else causes the problem.
Created ‎01-25-2017 08:56 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same error after using the new key. I believe the problem is the key pair as I am still not able to Putty into the ec2 instance using the public dns name or the ip. Is there another way to ssh from windows os?
14:26:05 UTC-0600ROLLBACK_IN_PROGRESSAWS::CloudFormation::StackAWSMPBASICCloudControllerwithnewVPCThe following resource(s) failed to create: [InstanceWaitCondition]. . Rollback requested by user.14:26:03 UTC-0600CREATE_FAILEDAWS::CloudFormation::WaitConditionInstanceWaitConditionWaitCondition received failed message: 'ERROR: command 'hdc create-credential --credential-name aws-access --role-arn $CREDENTIAL_ROLE_ARN --ssh-key-url http://169.254.169.254/latest/meta-data/public-keys/0/openssh-key --existing-ssh-key-pair $KEYPAIR_NAME' exited with status: 1 line: 1' for uniqueId: cbd-init14:19:01 UTC-0600CREATE_IN_PROGRESSAWS::CloudFormation::WaitConditionInstanceWaitConditionResource creation Initiated
