Closed vkvam closed 5 years ago
Hello!
Thanks for reporting this issue. Unfortunately the error output in this "diffs didn't match" situation is often not enough to diagnose the problem. Starting in 0.12 the situation that causes this error is more precisely reported, and the necessary debugging information is recorded in the logs. If this issue persists after upgrading Terraform, please file an issue with the referenced provider.
Thanks
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ECR: Use existing docker image ECR: image 431904215020.dkr.ecr.eu-west-1.amazonaws.com/vod-wowza:2018-11-01T14_04_32Z identified as latest image ASG: wowza-ecs-asg put in deploy mode Terraform: Workspace set to sandbox data.template_file.logstash_conf: Refreshing state... aws_s3_bucket_object.logstash_conf: Refreshing state... (ID: wowza/logstash/logstash_58119b967b207e738c7f855100477e7d.conf) aws_cloudwatch_log_group.ecs: Refreshing state... (ID: wowza-ecs-service/ecs-agent) aws_iam_role.wowza_task_role: Refreshing state... (ID: ecs-taskrole-wowza-ecs-service) aws_iam_role.ecs_autoscale_role: Refreshing state... (ID: wowza-ecs-service-autoscale-role) aws_cloudwatch_log_group.app: Refreshing state... (ID: wowza-ecs-service/app) aws_cloudwatch_log_group.logstash: Refreshing state... (ID: wowza-ecs-service/logstash) aws_iam_role.wowza_task_execution_role: Refreshing state... (ID: wowza-ecs-service-ecs-executionrole) data.template_file.wowza_task_policy_doc: Refreshing state... aws_iam_policy_attachment.ecs_autoscale_role_attach: Refreshing state... (ID: wowza-ecs-service-autoscale-role-attach) aws_iam_role_policy.wowza_task_execution_policy: Refreshing state... (ID: wowza-ecs-service-ecs-executionrole:wowza-ecs-service-ecs) aws_iam_role_policy.wowza_task_policy: Refreshing state... (ID: ecs-taskrole-wowza-ecs-service:ecs-taskrole-wowza-ecs-service) data.template_file.task_definition: Refreshing state... aws_ecs_task_definition.wowza: Refreshing state... (ID: wowza-ecs-service-task-definition) aws_ecs_service.wowza_service: Refreshing state... (ID: arn:aws:ecs:eu-west-1:518073743069:service/wowza-ecs-service-service) aws_appautoscaling_target.wowza_scale_target: Refreshing state... (ID: service/wowza-ecs-cluster/wowza-ecs-service-service) aws_appautoscaling_policy.wowza_up: Refreshing state... (ID: wowza-ecs-service-scale-up) aws_appautoscaling_policy.wowza_down: Refreshing state... (ID: wowza-ecs-service-scale-down) aws_cloudwatch_metric_alarm.wowza_service_high: Refreshing state... (ID: wowza-ecs-service-service-CPU-Utilization-High-30) aws_cloudwatch_metric_alarm.wowza_service_low: Refreshing state... (ID: wowza-ecs-service-service-CPU-Utilization-Low-5) aws_appautoscaling_target.wowza_scale_target: Destroying... (ID: service/wowza-ecs-cluster/wowza-ecs-service-service) aws_appautoscaling_target.wowza_scale_target: Destruction complete after 1s aws_ecs_service.wowza_service: Destroying... (ID: arn:aws:ecs:eu-west-1:518073743069:service/wowza-ecs-service-service) aws_ecs_service.wowza_service: Still destroying... (ID: arn:aws:ecs:eu-west-1:518073743069:service/wowza-ecs-service-service, 10s elapsed) aws_ecs_service.wowza_service: Still destroying... (ID: arn:aws:ecs:eu-west-1:518073743069:service/wowza-ecs-service-service, 20s elapsed) aws_ecs_service.wowza_service: Still destroying... (ID: arn:aws:ecs:eu-west-1:518073743069:service/wowza-ecs-service-service, 30s elapsed) aws_ecs_service.wowza_service: Destruction complete after 37s aws_ecs_service.wowza_service: Creating... cluster: "" => "arn:aws:ecs:eu-west-1:518073743069:cluster/wowza-ecs-cluster" deployment_maximum_percent: "" => "200" deployment_minimum_healthy_percent: "" => "100" desired_count: "" => "1" iam_role: "" => ""
launch_type: "" => "EC2"
name: "" => "wowza-ecs-service"
network_configuration.#: "" => "1"
network_configuration.0.assign_public_ip: "" => "false"
network_configuration.0.subnets.#: "" => "2"
network_configuration.0.subnets.2408863503: "" => "subnet-5c581a15"
network_configuration.0.subnets.3970046270: "" => "subnet-6dd9a10a"
ordered_placement_strategy.#: "" => "1"
ordered_placement_strategy.0.field: "" => "memory"
ordered_placement_strategy.0.type: "" => "binpack"
scheduling_strategy: "" => "REPLICA"
task_definition: "" => "arn:aws:ecs:eu-west-1:518073743069:task-definition/wowza-ecs-service-task-definition:33"
aws_ecs_service.wowza_service: Creation complete after 1s (ID: arn:aws:ecs:eu-west-1:518073743069:service/wowza-ecs-service)
aws_appautoscaling_target.wowza_scale_target: Creating...
max_capacity: "" => "4"
min_capacity: "" => "1"
resource_id: "" => "service/wowza-ecs-cluster/wowza-ecs-service"
role_arn: "" => "arn:aws:iam::518073743069:role/wowza-ecs-service-autoscale-role"
scalable_dimension: "" => "ecs:service:DesiredCount"
service_namespace: "" => "ecs"
aws_appautoscaling_target.wowza_scale_target: Creation complete after 0s (ID: service/wowza-ecs-cluster/wowza-ecs-service)
aws_appautoscaling_policy.wowza_down: Modifying... (ID: wowza-ecs-service-scale-down)
resource_id: "service/wowza-ecs-cluster/wowza-ecs-service-service" => "service/wowza-ecs-cluster/wowza-ecs-service"
aws_appautoscaling_policy.wowza_up: Modifying... (ID: wowza-ecs-service-scale-up)
resource_id: "service/wowza-ecs-cluster/wowza-ecs-service-service" => "service/wowza-ecs-cluster/wowza-ecs-service"
aws_appautoscaling_policy.wowza_up: Modifications complete after 1s (ID: wowza-ecs-service-scale-up)
aws_appautoscaling_policy.wowza_down: Modifications complete after 1s (ID: wowza-ecs-service-scale-down)
Error: Error applying plan:
2 error(s) occurred:
Please include the following information in your report:
Also include as much context as you can about your config, state, and the steps you performed to trigger this error.
Please include the following information in your report:
Also include as much context as you can about your config, state, and the steps you performed to trigger this error.
Terraform does not automatically rollback in the face of errors. Instead, your Terraform state file has been partially updated with any resources that successfully completed. Please address the error above and apply again to incrementally change your infrastructure.