hashicorp / terraform-provider-aws

The AWS Provider enables Terraform to manage AWS resources.
https://registry.terraform.io/providers/hashicorp/aws
Mozilla Public License 2.0
9.84k stars 9.19k forks source link

v0.11.9 crash report: Possible crash when aws_lb_listener cognito action is removed #6256

Closed ghost closed 6 years ago

ghost commented 6 years ago

This issue was originally opened by @brett-richardson as hashicorp/terraform#19187. It was migrated here as a result of the provider split. The original body of the issue is below.


Terraform Version

Terraform v0.11.9
+ provider.archive v1.0.3
+ provider.aws v1.40.0
+ provider.dns v2.0.0
+ provider.local v1.1.0
+ provider.template v1.0.0
+ provider.tls v1.1.0

Terraform Configuration Files

Available privately if required.

Debug Output

Crash Output

2018/10/24 11:01:14 [DEBUG] [aws-sdk-go] {}
2018/10/24 11:01:14 [DEBUG] plugin: waiting for all plugin processes to complete...
2018-10-24T11:01:14.616+0100 [WARN ] plugin: error closing client during Kill: err="connection is shut down"
2018-10-24T11:01:14.617+0100 [DEBUG] plugin.terraform-provider-template_v1.0.0_x4: 2018/10/24 11:01:14 [ERR] plugin: plugin server: accept unix /var/folders/l3/82rjb1ys5ybc9yr574w468mh0000gn/T/plugin111714273: use of closed network connection
2018-10-24T11:01:14.621+0100 [DEBUG] plugin: plugin process exited: path=/terraform/staging/.terraform/plugins/darwin_amd64/terraform-provider-dns_v2.0.0_x4
2018-10-24T11:01:14.622+0100 [DEBUG] plugin: plugin process exited: path=/terraform/staging/.terraform/plugins/darwin_amd64/terraform-provider-local_v1.1.0_x4
2018-10-24T11:01:14.622+0100 [DEBUG] plugin: plugin process exited: path=/terraform/staging/.terraform/plugins/darwin_amd64/terraform-provider-archive_v1.0.0_x4
2018-10-24T11:01:14.622+0100 [DEBUG] plugin: plugin process exited: path=/terraform/staging/.terraform/plugins/darwin_amd64/terraform-provider-template_v1.0.0_x4

* module.satellite_singapore.aws_cloudwatch_metric_alarm.ghost_cpu_high: 1 error(s) occurred:

* module.satellite_singapore.aws_cloudwatch_metric_alarm.ghost_cpu_high: aws_cloudwatch_metric_alarm.ghost_cpu_high: connection is shut down
* module.satellite_singapore.module.regional_network.aws_subnet.private_a: 1 error(s) occurred:

* module.satellite_singapore.module.regional_network.aws_subnet.private_a: aws_subnet.private_a: unexpected EOF
* module.tooling_cluster.module.tooling_services.aws_ecs_service.sensu_server: 1 error(s) occurred:

* module.tooling_cluster.module.tooling_services.aws_ecs_service.sensu_server: aws_ecs_service.sensu_server: connection is shut down

Expected Behavior

Terraform command displays planned changed.

Actual Behavior

Terraform crashes before prompting to apply.

Steps to Reproduce

Configuration private.

I think possibly it was related to the new addition of Cognito support in the aws_lb_listener resource. I created a listener action of type "authenticate-cognito" in Terraform and then removed it manually.

Can confirm that manually recreating the cognito listener action allows Terraform to run without error again.

tomelliff commented 6 years ago

@brett-richardson Can you reliably reproduce this? The error looks like it's just your connection is dying when Terraform is talking to the AWS API.

If you can it would be useful if you could provide a minimally verifiable example that does regularly reproduce this error.

bflad commented 6 years ago

Bug fix pull request submitted: #6319

bflad commented 6 years ago

The fix for actions deleted outside Terraform has been merged and will release with version 1.43.0 of the AWS provider, likely middle of next week. 👍

bflad commented 6 years ago

This has been released in version 1.43.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

ghost commented 4 years ago

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!