作者：蒋筱谷_680 | 来源：互联网 | 2023-09-18 13:05
This issue was originally opened by as hashicorp/terraform#10689. It was migrated here as part of the provider split. The original body of the issue is below.
Terraform Version
Terraform v0.7.7
Affected Resource(s)
- aws_cloudwatch_metric_alarm
Terraform Configuration Files
I have three modules that create CloudWatch alarms: CPU usage, one for memory usage, and one for disk space usage. They all look more or less like this:
1
2
3
4
5
6
7
| hcl
resource "aws_cloudwatch_metric_alarm" "ec2_high_cpu_utilization" {
count &＃061; "${var.instance_count}"
alarm_name &＃061; "ec2-high-cpu-utilization-${element(var.instance_ids, count.index)}"
# (... all the standard alarm params ...)
} |
Expected Behavior
I'm passing these modules the ID of the same EC2 Instance, so I expect three alarms to be created.
Actual Behavior
The memory usage alarm gets created, but the other two fail with this error:
1
2
3
4
| * aws_cloudwatch_metric_alarm.ec2_high_disk_utilization: Creating metric alarm failed: ValidationError: A separate request to update this alarm is in progress.
status code: 400, request id: dafd60e0-c0de-11e6-be81-87349c242d9e
* aws_cloudwatch_metric_alarm.ec2_high_cpu_utilization: Creating metric alarm failed: ValidationError: A separate request to update this alarm is in progress.
status code: 400, request id: db0242e5-c0de-11e6-903c-8b6cee93e201 |
No other alarms exist in my account whatsoever. No one else is using the account at all, so there are no other API calls happening.
Steps to Reproduce
Important Factoids
When I re-ran
after the error, the two alarms were created just fine.
该提问来源于开源项目：hashicorp/terraform-provider-aws
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!
京公网安备 11010802041100号