Skip to content
This repository has been archived by the owner on Jan 4, 2024. It is now read-only.

Repeatable #2

Closed
daneroo opened this issue Oct 4, 2016 · 7 comments
Closed

Repeatable #2

daneroo opened this issue Oct 4, 2016 · 7 comments

Comments

@daneroo
Copy link

daneroo commented Oct 4, 2016

I may well be doing something wrong,
but I cannot invoke the Stack creation twice with the same name.

That is:

  • I bring up the stack (Using the Launch Stack button)
  • Then completely delete it.
  • I can then Launch an identical stack but not if I re-use the same Stack Name.

I can't for the life of me find any dangling resources which may still be present.
This is the error message in the Cloudformation Events tab:

19:35:28 UTC-0400   ROLLBACK_IN_PROGRESS    AWS::CloudFormation::Stack  RefTest The following resource(s) failed to create: [ALB, ECS]. . Rollback requested by user.

Any Ideas?

@cloudoperator
Copy link

I am facing the same issue! Be nice to know what the issue is.

@JustinPlute
Copy link

+1

@daneroo
Copy link
Author

daneroo commented Oct 6, 2016

I have managed to work around the problem for now,

  • After cloning the s3 bucket to experiment
  • Provisioning with aws cloudformation [create|update|delete]-stack, with explicit:
    • --role-arn w/ Admin privileges, as well as
    • --capabilities CAPABILITY_IAM CAPABILITY_NAMED_IAM

But the clincher seems to be removing the infrastructure.yml::ECSCluster CusterName property

ECSCluster:
    Type: AWS::ECS::Cluster
    # Here be dragons, this is causing stack failures on update, or re-provisioning after delete.
    # Properties:
    #     ClusterName: !Ref EnvironmentName

This is not ideal because the Cluster Name is no longer predictable, and is harder to use from my evolving, but independant deploy scripts...

@PaulMaddox
Copy link
Contributor

Thank you for reporting this. You are correct that this is related to the ClusterName parameter. The ECS/CloudFormation teams are aware and working on a fix.

@kalpik
Copy link

kalpik commented Oct 14, 2016

Any updates on how it's going? :)

@PaulMaddox
Copy link
Contributor

Thanks again for reporting this. I believe this has now been resolved by the CloudFormation team.

I have tested by:

  1. Deploying the stack to us-east-2 (Ohio)
  2. Deleting the whole stack
  3. Deploying the stack again, with the same stack name (successfully)

If you're still having problems, please re-open this issue.

PaulMaddox pushed a commit that referenced this issue Nov 24, 2018
Added CloudWatch Unified Agent
Removed CloudWatch Logs (only) Agent
Added SSM and CWAgent managed policies to ECS Role
Added ECS CloudWatch Parameter
Default Logs: unchanged from previous CloudWatch Logs Agent implementation
Default Metrics: Root Volume % used, Memory % Used
@stevenlafl
Copy link

Same exact problem, newest version of this repository.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants