The following resource(s) failed to create: [DeterminedAddress] about determined

[neilconway]

@sbhonde1 Thanks for the report! Can you post the complete output that is produced by det-deploy? Might be easier to understand what is going on with --deployment-type simple first and then we can investigate the vpc case later.

[seanr15]

The Cloudformation console might have more information on why the resource failed to create. You should see a stack there named testcluster0. It could be that you are already at your Elastic IP (EIP) quota if the DeterminedAddress was the only failing resource. Both vpc and simple attach an EIP to the Determined master instance.

[sbhonde1]

@neilconway @seanr15 Thank you for the quick response.
I was able to run det-deploy using a secure type. However, I got the following message on CloudFormation when I ran with vpc :

You must specify an allocation id when mapping an address to a VPC instance (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterCombination;

[seanr15]

The CloudFormation templates behind det-deploy were not designed to run from one deployment type to another. If you ran det-deploy aws up --deployment-type vpc and then followed with det-deploy aws up --deployment-type secure, there is a good chance your deployment is in a funky state. I recommend running det-deploy aws down to remove the resources and try again using det-deploy aws up --deployment-type simple.

[sbhonde1]

I am totally new to this so I think it was in a funny state. I was not able to connect to the master. Is there any way exist to check if I am able to connect/ping to master?

I got the following error when I tried to deploy using --deployment-type simple:

The following resource(s) failed to create: [DatabaseEgress, AgentSecurityGroupEgress, Database, MasterSecurityGroupInternet, MasterSecurityGroupEgress, DatabaseIngress, AgentRole, CheckpointBucket]

Only Amazon VPC security groups may be used with this operation. (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterValue

Subnet group name can not be blank. (Service: AmazonRDS; Status Code: 400; Error Code: InvalidParameterValue;)

[seanr15]

Interesting. Seems like things are still in a strange state.

Are you on our community slack channel (determined-community.slack.com)? I can hop on a slack call to get you unblocked. Send me a DM - sean.determined

[sbhonde1]

Hi Sean,
I tried reaching out but I think I do not have access to slack group. Also, I am not able to login using my personal slack account.

[seanr15]

Use this link to join

[sbhonde1]

The issue was caused because of internal aws setup. The --deployment-type secure is working fine so closing this for now. I will comment if I find the exact reason.