Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-apply of timed out ASG creation does not enable requested CloudWatch metrics #604

Closed
hashibot opened this issue Jun 13, 2017 · 2 comments
Labels
bug Addresses a defect in current functionality. service/autoscaling Issues and PRs that pertain to the autoscaling service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@hashibot
Copy link

This issue was originally opened by @mattzimmerman as hashicorp/terraform#12654. It was migrated here as part of the provider split. The original body of the issue is below.


Terraform Version

Terraform 0.8.4
edit also confirmed that we still see this issue on 0.8.7

Affected Resource(s)

Please list the resources as a list, for example:

  • aws_autoscaling_group

Debug Output

Run hashicorp/terraform#1 (initial plan): https://gist.github.com/mattzimmerman/b301b0a230e51544b53b535392d577c3
Run hashicorp/terraform#1 (apply): https://gist.github.com/mattzimmerman/08eefb57d56f49e3985ce8579ed18dd3
Run hashicorp/terraform#2 (retry after a failure): https://gist.github.com/mattzimmerman/9d6cb45daede7378cfda77079c8094a5

Expected Behavior

Re-apply of failed ASG creations should detect that requested CloudWatch metrics were missing and enable them.

Actual Behavior

CloudWatch metrics are not enabled before the ASG has healthy instances. After the timeout failure, no diff was detected on a re-apply (so CloudWatch metrics are never enabled on the ASG resource during subsequent applies if it fails the first time).

Steps to Reproduce

  1. Apply an aws_autoscaling_group with an ELB healthcheck and CloudWatch GroupInServiceInstances enabled via a module. None of the instances ever become healthy, so creation of the ASG should fail after the timeout.
  2. Re-apply that same aws_autoscaling_group.
  3. Notice that no diff is detected, but CloudWatch metrics are not enabled on that ASG.
@hashibot hashibot added the bug Addresses a defect in current functionality. label Jun 13, 2017
@radeksimko radeksimko added the service/autoscaling Issues and PRs that pertain to the autoscaling service. label Jan 27, 2018
@github-actions
Copy link

github-actions bot commented Apr 2, 2020

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Apr 2, 2020
@github-actions github-actions bot closed this as completed May 3, 2020
@ghost
Copy link

ghost commented Jun 3, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Jun 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/autoscaling Issues and PRs that pertain to the autoscaling service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

No branches or pull requests

2 participants