Terraform AWS Provider plugin v2.64.0 failed on err: unexpected EOF panic: unknown value type in TypeMap bool
#13549
Comments
github-actions
bot
added
the
needs-triage
izzyleung
changed the title
eval: *terraform.EvalSequence, err: unexpected EOF
ghost
added
bug
izzyleung
changed the title
eval: *terraform.EvalSequence, err: unexpected EOFerr: unexpected EOF panic: unknown value type in TypeMap bool
|
Same issue with below setup: |
|
We are also facing the same Issue. Terraform: 0.11 panic: unknown value type in TypeMap bool We haven't faced any issue with the below versions. Terraform: 0.11 |
|
Facing same issue, too. We temporary make the tags = [
{
key = "env"
value = "prod"
propagate_at_launch = "true"
}
]Since terraform 0.11 document mentions:
reference: |
|
Related:
This is the relevant code around the panic: |
bflad
added
service/autoscaling
Thanks for sharing the details |
|
Quick question: Is anyone experiencing this with Terraform 0.12? |
Reference: hashicorp/terraform-provider-aws#13549 This may only be an issue with Terraform 0.11 and earlier with an obscure schema of: ```go "attr": { Type: schema.TypeSet, Optional: true, Elem: &schema.Schema{ Type: schema.TypeMap, Elem: &schema.Schema{ Type: schema.TypeString, }, }, ``` Previously, this would panic (with updated test): ```console $ go test ./helper/schema -run=TestSerializeForHash --- FAIL: TestSerializeForHash (0.00s) panic: unknown value type in TypeMap bool [recovered] panic: unknown value type in TypeMap bool goroutine 5 [running]: testing.tRunner.func1.1(0x1a4a5e0, 0xc0004b9920) /usr/local/Cellar/go/1.14.3/libexec/src/testing/testing.go:940 +0x2f5 testing.tRunner.func1(0xc000372c60) /usr/local/Cellar/go/1.14.3/libexec/src/testing/testing.go:943 +0x3f9 panic(0x1a4a5e0, 0xc0004b9920) /usr/local/Cellar/go/1.14.3/libexec/src/runtime/panic.go:969 +0x166 github.com/hashicorp/terraform-plugin-sdk/helper/schema.SerializeValueForHash(0xc000085bb8, 0x1aaef40, 0xc000528450, 0xc000531400) /Users/bflad/src/github.com/hashicorp/terraform-plugin-sdk/helper/schema/serialize.go:61 +0x8c9 github.com/hashicorp/terraform-plugin-sdk/helper/schema.TestSerializeForHash(0xc000372c60) /Users/bflad/src/github.com/hashicorp/terraform-plugin-sdk/helper/schema/serialize_test.go:230 +0x1520 testing.tRunner(0xc000372c60, 0x1c2e848) /usr/local/Cellar/go/1.14.3/libexec/src/testing/testing.go:991 +0xdc created by testing.(*T).Run /usr/local/Cellar/go/1.14.3/libexec/src/testing/testing.go:1042 +0x357 FAIL github.com/hashicorp/terraform-plugin-sdk/helper/schema 5.797s ```
Reference: hashicorp/terraform-provider-aws#13549 This may only be an issue with Terraform 0.11 and earlier with an obscure schema of: ```go "attr": { Type: schema.TypeSet, Optional: true, Elem: &schema.Schema{ Type: schema.TypeMap, Elem: &schema.Schema{ Type: schema.TypeString, }, }, ``` Previously, this would panic (with updated test): ```console $ go test ./helper/schema -run=TestSerializeForHash --- FAIL: TestSerializeForHash (0.00s) panic: unknown value type in TypeMap bool [recovered] panic: unknown value type in TypeMap bool goroutine 5 [running]: testing.tRunner.func1.1(0x1a4a5e0, 0xc0004b9920) /usr/local/Cellar/go/1.14.3/libexec/src/testing/testing.go:940 +0x2f5 testing.tRunner.func1(0xc000372c60) /usr/local/Cellar/go/1.14.3/libexec/src/testing/testing.go:943 +0x3f9 panic(0x1a4a5e0, 0xc0004b9920) /usr/local/Cellar/go/1.14.3/libexec/src/runtime/panic.go:969 +0x166 github.com/hashicorp/terraform-plugin-sdk/helper/schema.SerializeValueForHash(0xc000085bb8, 0x1aaef40, 0xc000528450, 0xc000531400) /Users/bflad/src/github.com/hashicorp/terraform-plugin-sdk/helper/schema/serialize.go:61 +0x8c9 github.com/hashicorp/terraform-plugin-sdk/helper/schema.TestSerializeForHash(0xc000372c60) /Users/bflad/src/github.com/hashicorp/terraform-plugin-sdk/helper/schema/serialize_test.go:230 +0x1520 testing.tRunner(0xc000372c60, 0x1c2e848) /usr/local/Cellar/go/1.14.3/libexec/src/testing/testing.go:991 +0xdc created by testing.(*T).Run /usr/local/Cellar/go/1.14.3/libexec/src/testing/testing.go:1042 +0x357 FAIL github.com/hashicorp/terraform-plugin-sdk/helper/schema 5.797s ```
|
Same issue with:
|
I tested with terraform 0.12.20 and 0.12.26 with no problems. |
|
Same issue with 0.11.13 and 2.64 |
1 similar comment
|
Same issue with 0.11.13 and 2.64 |
|
Same issue with: Terraform: v0.11.14 |
|
One of my team members found that if we change propagate_on_launch = true to propagate_on_launch = "true" it works around this issue. |
|
Same issue with terraform v0.11.11 and aws provider 2.64.0 |
|
Same issue with terraform v0.11.11 and aws provider 2.64.0 22:14:25 panic: unknown value type in TypeMap bool |
|
Hi folks 👋 Please note that the fix for this crash (verified with Terraform CLI v0.11.14) has been merged and will release with version 2.65.0 of the Terraform AWS Provider, later today. 👍 |
|
This has been released in version 2.65.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
|
This might be fixed in 2.65.0, but that version is also broken in another way. Can we get a bug fix release without any additional cruft? |
…gs` for Terraform 0.11 and earlier with boolean `propagate_at_launch` values Reference: #13312 Reference: #13360 Reference: #13469 Reference: #13549 Reference: #13635 One of the major improvements internally with Terraform 0.12's type system is that providers and the core logic agree on a resource schema and its normalization during configuration parsing so the state and difference handling is more consistent. In Terraform 0.11 and earlier, a quirky behavior with raw boolean values is that they could be converted to string "0" and "1" values based on various factors such as passing through functions. With recent changes to the `aws_autoscaling_group` resource to fix its handling of the `tags` attribute (to prevent `d.Set()` errors and testing panics in the upcoming Terraform Plugin SDK 2.0.0), this behavior was highlighted as unexpected perpetual differences. This cannot be caught in the 0.12 shimmed acceptance testing framework and therefore is manually tested by the below configuration and reproduction steps. **NOTE:** The `tags` argument will be deprecated and removed in a future major version of the Terraform AWS Provider since it was designed as a workaround for Terraform 0.11 and earlier configurations. There are very few, if any, other Terraform AWS Provider attributes represented as a set of maps. In Terraform 0.12 and later, the `tag` argument more appropriately represents Auto Scaling Group resource tags as configuration blocks with strongly typed nested arguments and can be dynamically built via the `dynamic` configuration language feature. That deprecation is out of scope for this changeset though and likely will not occur until after Terraform AWS Provider version 3.0.0. Given the following Terraform 0.11 compatible configuration with raw boolean values: ```hcl terraform { required_version = "0.11.14" } provider "aws" { region = "us-east-2" version = "2.67.0" } locals { test = [ { key = "localkey1" value = "localvalue1" propagate_at_launch = true }, { key = "localkey2" value = "localvalue2" propagate_at_launch = true }, ] } data "aws_ami" "test" { most_recent = true owners = ["amazon"] filter { name = "name" values = ["amzn-ami-hvm-*-x86_64-gp2"] } } data "aws_availability_zones" "available" { state = "available" filter { name = "opt-in-status" values = ["opt-in-not-required"] } } resource "aws_launch_template" "test" { name_prefix = "test" image_id = "${data.aws_ami.test.id}" instance_type = "t2.micro" } resource "aws_autoscaling_group" "test" { availability_zones = ["${data.aws_availability_zones.available.names[0]}"] desired_capacity = 0 max_size = 0 min_size = 0 tags = ["${concat(list(map("key", "resourcekey1", "value", "resourcevalue1", "propagate_at_launch", true)), local.test)}"] launch_template { id = "${aws_launch_template.test.id}" version = "${aws_launch_template.test.default_version}" } } output "tags" { value = "${aws_autoscaling_group.test.tags}" } ``` Applying twice has a perpetual difference: ```console $ terraform0.11.14 init Initializing provider plugins... - Checking for available provider plugins on https://releases.hashicorp.com... - Downloading plugin for provider "aws" (2.67.0)... Terraform has been successfully initialized! You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure. All Terraform commands should now work. If you ever set or change modules or backend configuration for Terraform, rerun this command to reinitialize your working directory. If you forget, other commands will detect it and remind you to do so if necessary. $ terraform0.11.14 apply data.aws_ami.test: Refreshing state... data.aws_availability_zones.available: Refreshing state... An execution plan has been generated and is shown below. Resource actions are indicated with the following symbols: + create Terraform will perform the following actions: + aws_autoscaling_group.test id: <computed> arn: <computed> availability_zones.#: "1" availability_zones.4293815384: "us-east-2a" default_cooldown: <computed> desired_capacity: "0" force_delete: "false" health_check_grace_period: "300" health_check_type: <computed> launch_template.#: "1" launch_template.0.id: "${aws_launch_template.test.id}" launch_template.0.name: <computed> launch_template.0.version: "${aws_launch_template.test.default_version}" load_balancers.#: <computed> max_size: "0" metrics_granularity: "1Minute" min_size: "0" name: <computed> protect_from_scale_in: "false" service_linked_role_arn: <computed> tags.#: "3" tags.2825254636.%: "3" tags.2825254636.key: "localkey1" tags.2825254636.propagate_at_launch: "1" tags.2825254636.value: "localvalue1" tags.2888644505.%: "3" tags.2888644505.key: "resourcekey1" tags.2888644505.propagate_at_launch: "1" tags.2888644505.value: "resourcevalue1" tags.3299348900.%: "3" tags.3299348900.key: "localkey2" tags.3299348900.propagate_at_launch: "1" tags.3299348900.value: "localvalue2" target_group_arns.#: <computed> vpc_zone_identifier.#: <computed> wait_for_capacity_timeout: "10m" + aws_launch_template.test id: <computed> arn: <computed> default_version: <computed> image_id: "ami-083ebc5a49573896a" instance_type: "t2.micro" latest_version: "0" metadata_options.#: <computed> name: <computed> name_prefix: "test" Plan: 2 to add, 0 to change, 0 to destroy. Do you want to perform these actions? Terraform will perform the actions described above. Only 'yes' will be accepted to approve. Enter a value: yes aws_launch_template.test: Creating... arn: "" => "<computed>" default_version: "" => "<computed>" image_id: "" => "ami-083ebc5a49573896a" instance_type: "" => "t2.micro" latest_version: "" => "<computed>" metadata_options.#: "" => "<computed>" name: "" => "<computed>" name_prefix: "" => "test" aws_launch_template.test: Creation complete after 0s (ID: lt-0d8e6f4f94a683778) aws_autoscaling_group.test: Creating... arn: "" => "<computed>" availability_zones.#: "" => "1" availability_zones.4293815384: "" => "us-east-2a" default_cooldown: "" => "<computed>" desired_capacity: "" => "0" force_delete: "" => "false" health_check_grace_period: "" => "300" health_check_type: "" => "<computed>" launch_template.#: "" => "1" launch_template.0.id: "" => "lt-0d8e6f4f94a683778" launch_template.0.name: "" => "<computed>" launch_template.0.version: "" => "1" load_balancers.#: "" => "<computed>" max_size: "" => "0" metrics_granularity: "" => "1Minute" min_size: "" => "0" name: "" => "<computed>" protect_from_scale_in: "" => "false" service_linked_role_arn: "" => "<computed>" tags.#: "" => "3" tags.2825254636.%: "" => "3" tags.2825254636.key: "" => "localkey1" tags.2825254636.propagate_at_launch: "" => "1" tags.2825254636.value: "" => "localvalue1" tags.2888644505.%: "" => "3" tags.2888644505.key: "" => "resourcekey1" tags.2888644505.propagate_at_launch: "" => "1" tags.2888644505.value: "" => "resourcevalue1" tags.3299348900.%: "" => "3" tags.3299348900.key: "" => "localkey2" tags.3299348900.propagate_at_launch: "" => "1" tags.3299348900.value: "" => "localvalue2" target_group_arns.#: "" => "<computed>" vpc_zone_identifier.#: "" => "<computed>" wait_for_capacity_timeout: "" => "10m" aws_autoscaling_group.test: Creation complete after 2s (ID: tf-asg-20200623194008467200000003) Apply complete! Resources: 2 added, 0 changed, 0 destroyed. Outputs: tags = [ { key = localkey2, propagate_at_launch = 1, value = localvalue2 }, { key = localkey1, propagate_at_launch = 1, value = localvalue1 }, { key = resourcekey1, propagate_at_launch = 1, value = resourcevalue1 } ] $ terraform0.11.14 apply data.aws_ami.test: Refreshing state... data.aws_availability_zones.available: Refreshing state... aws_launch_template.test: Refreshing state... (ID: lt-0d8e6f4f94a683778) aws_autoscaling_group.test: Refreshing state... (ID: tf-asg-20200623194008467200000003) An execution plan has been generated and is shown below. Resource actions are indicated with the following symbols: ~ update in-place Terraform will perform the following actions: ~ aws_autoscaling_group.test tags.2131493069.%: "3" => "0" tags.2131493069.key: "localkey2" => "" tags.2131493069.propagate_at_launch: "true" => "" tags.2131493069.value: "localvalue2" => "" tags.2825254636.%: "0" => "3" tags.2825254636.key: "" => "localkey1" tags.2825254636.propagate_at_launch: "" => "1" tags.2825254636.value: "" => "localvalue1" tags.2888644505.%: "0" => "3" tags.2888644505.key: "" => "resourcekey1" tags.2888644505.propagate_at_launch: "" => "1" tags.2888644505.value: "" => "resourcevalue1" tags.3299348900.%: "0" => "3" tags.3299348900.key: "" => "localkey2" tags.3299348900.propagate_at_launch: "" => "1" tags.3299348900.value: "" => "localvalue2" tags.3593646732.%: "3" => "0" tags.3593646732.key: "localkey1" => "" tags.3593646732.propagate_at_launch: "true" => "" tags.3593646732.value: "localvalue1" => "" tags.3707627218.%: "3" => "0" tags.3707627218.key: "resourcekey1" => "" tags.3707627218.propagate_at_launch: "true" => "" tags.3707627218.value: "resourcevalue1" => "" Plan: 0 to add, 1 to change, 0 to destroy. ``` Building this version of the provider, the difference is no longer present: ```console $ cp ~/go/bin/terraform-provider-aws .terraform/plugins/darwin_amd64/terraform-provider-aws_v2.67.0_x4; terraform0.11.14 init; terraform0.11.14 apply Initializing provider plugins... Terraform has been successfully initialized! You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure. All Terraform commands should now work. If you ever set or change modules or backend configuration for Terraform, rerun this command to reinitialize your working directory. If you forget, other commands will detect it and remind you to do so if necessary. data.aws_availability_zones.available: Refreshing state... data.aws_ami.test: Refreshing state... aws_launch_template.test: Refreshing state... (ID: lt-0d8e6f4f94a683778) aws_autoscaling_group.test: Refreshing state... (ID: tf-asg-20200623194008467200000003) Apply complete! Resources: 0 added, 0 changed, 0 destroyed. Outputs: tags = [ { key = localkey1, propagate_at_launch = 1, value = localvalue1 }, { key = resourcekey1, propagate_at_launch = 1, value = resourcevalue1 }, { key = localkey2, propagate_at_launch = 1, value = localvalue2 } ] ``` Output from acceptance testing (Terraform 0.12 compatible): ``` --- PASS: TestAccAWSAutoScalingGroup_ALB_TargetGroups (176.05s) --- PASS: TestAccAWSAutoScalingGroup_ALB_TargetGroups_ELBCapacity (342.40s) --- PASS: TestAccAWSAutoScalingGroup_autoGeneratedName (89.91s) --- PASS: TestAccAWSAutoScalingGroup_basic (259.25s) --- PASS: TestAccAWSAutoScalingGroup_classicVpcZoneIdentifier (93.45s) --- PASS: TestAccAWSAutoScalingGroup_emptyAvailabilityZones (92.72s) --- PASS: TestAccAWSAutoScalingGroup_enablingMetrics (174.98s) --- PASS: TestAccAWSAutoScalingGroup_initialLifecycleHook (271.36s) --- PASS: TestAccAWSAutoScalingGroup_launchTemplate (62.35s) --- PASS: TestAccAWSAutoScalingGroup_LaunchTemplate_IAMInstanceProfile (61.69s) --- PASS: TestAccAWSAutoScalingGroup_launchTemplate_update (143.24s) --- PASS: TestAccAWSAutoScalingGroup_launchTempPartitionNum (77.30s) --- PASS: TestAccAWSAutoScalingGroup_LoadBalancers (695.77s) --- PASS: TestAccAWSAutoScalingGroup_MaxInstanceLifetime (80.89s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy (108.93s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_InstancesDistribution_OnDemandAllocationStrategy (49.98s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_InstancesDistribution_OnDemandBaseCapacity (82.14s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_InstancesDistribution_OnDemandPercentageAboveBaseCapacity (96.59s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_InstancesDistribution_SpotAllocationStrategy (83.60s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_InstancesDistribution_SpotInstancePools (90.32s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_InstancesDistribution_SpotMaxPrice (112.90s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_InstancesDistribution_UpdateToZeroOnDemandBaseCapacity (73.62s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_LaunchTemplate_LaunchTemplateSpecification_LaunchTemplateName (86.69s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_LaunchTemplate_LaunchTemplateSpecification_Version (85.84s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_LaunchTemplate_Override_InstanceType (85.29s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_LaunchTemplate_Override_WeightedCapacity (205.06s) --- PASS: TestAccAWSAutoScalingGroup_namePrefix (45.70s) --- PASS: TestAccAWSAutoScalingGroup_serviceLinkedRoleARN (83.67s) --- PASS: TestAccAWSAutoScalingGroup_suspendingProcesses (267.51s) --- PASS: TestAccAWSAutoScalingGroup_tags (299.92s) --- PASS: TestAccAWSAutoScalingGroup_TargetGroupArns (249.92s) --- PASS: TestAccAWSAutoScalingGroup_terminationPolicies (151.45s) --- PASS: TestAccAWSAutoScalingGroup_VpcUpdates (236.40s) --- PASS: TestAccAWSAutoScalingGroup_WithLoadBalancer (389.18s) --- PASS: TestAccAWSAutoScalingGroup_WithLoadBalancer_ToTargetGroup (384.27s) --- PASS: TestAccAWSAutoScalingGroup_withMetrics (96.85s) --- PASS: TestAccAWSAutoScalingGroup_withPlacementGroup (200.69s) ```
…gs` for Terraform 0.11 and earlier with boolean `propagate_at_launch` values (#13912) Reference: #13312 Reference: #13360 Reference: #13469 Reference: #13549 Reference: #13635 One of the major improvements internally with Terraform 0.12's type system is that providers and the core logic agree on a resource schema and its normalization during configuration parsing so the state and difference handling is more consistent. In Terraform 0.11 and earlier, a quirky behavior with raw boolean values is that they could be converted to string "0" and "1" values based on various factors such as passing through functions. With recent changes to the `aws_autoscaling_group` resource to fix its handling of the `tags` attribute (to prevent `d.Set()` errors and testing panics in the upcoming Terraform Plugin SDK 2.0.0), this behavior was highlighted as unexpected perpetual differences. This cannot be caught in the 0.12 shimmed acceptance testing framework and therefore is manually tested by the below configuration and reproduction steps. **NOTE:** The `tags` argument will be deprecated and removed in a future major version of the Terraform AWS Provider since it was designed as a workaround for Terraform 0.11 and earlier configurations. There are very few, if any, other Terraform AWS Provider attributes represented as a set of maps. In Terraform 0.12 and later, the `tag` argument more appropriately represents Auto Scaling Group resource tags as configuration blocks with strongly typed nested arguments and can be dynamically built via the `dynamic` configuration language feature. That deprecation is out of scope for this changeset though and likely will not occur until after Terraform AWS Provider version 3.0.0. Given the following Terraform 0.11 compatible configuration with raw boolean values: ```hcl terraform { required_version = "0.11.14" } provider "aws" { region = "us-east-2" version = "2.67.0" } locals { test = [ { key = "localkey1" value = "localvalue1" propagate_at_launch = true }, { key = "localkey2" value = "localvalue2" propagate_at_launch = true }, ] } data "aws_ami" "test" { most_recent = true owners = ["amazon"] filter { name = "name" values = ["amzn-ami-hvm-*-x86_64-gp2"] } } data "aws_availability_zones" "available" { state = "available" filter { name = "opt-in-status" values = ["opt-in-not-required"] } } resource "aws_launch_template" "test" { name_prefix = "test" image_id = "${data.aws_ami.test.id}" instance_type = "t2.micro" } resource "aws_autoscaling_group" "test" { availability_zones = ["${data.aws_availability_zones.available.names[0]}"] desired_capacity = 0 max_size = 0 min_size = 0 tags = ["${concat(list(map("key", "resourcekey1", "value", "resourcevalue1", "propagate_at_launch", true)), local.test)}"] launch_template { id = "${aws_launch_template.test.id}" version = "${aws_launch_template.test.default_version}" } } output "tags" { value = "${aws_autoscaling_group.test.tags}" } ``` Applying twice has a perpetual difference: ```console $ terraform0.11.14 init Initializing provider plugins... - Checking for available provider plugins on https://releases.hashicorp.com... - Downloading plugin for provider "aws" (2.67.0)... Terraform has been successfully initialized! You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure. All Terraform commands should now work. If you ever set or change modules or backend configuration for Terraform, rerun this command to reinitialize your working directory. If you forget, other commands will detect it and remind you to do so if necessary. $ terraform0.11.14 apply data.aws_ami.test: Refreshing state... data.aws_availability_zones.available: Refreshing state... An execution plan has been generated and is shown below. Resource actions are indicated with the following symbols: + create Terraform will perform the following actions: + aws_autoscaling_group.test id: <computed> arn: <computed> availability_zones.#: "1" availability_zones.4293815384: "us-east-2a" default_cooldown: <computed> desired_capacity: "0" force_delete: "false" health_check_grace_period: "300" health_check_type: <computed> launch_template.#: "1" launch_template.0.id: "${aws_launch_template.test.id}" launch_template.0.name: <computed> launch_template.0.version: "${aws_launch_template.test.default_version}" load_balancers.#: <computed> max_size: "0" metrics_granularity: "1Minute" min_size: "0" name: <computed> protect_from_scale_in: "false" service_linked_role_arn: <computed> tags.#: "3" tags.2825254636.%: "3" tags.2825254636.key: "localkey1" tags.2825254636.propagate_at_launch: "1" tags.2825254636.value: "localvalue1" tags.2888644505.%: "3" tags.2888644505.key: "resourcekey1" tags.2888644505.propagate_at_launch: "1" tags.2888644505.value: "resourcevalue1" tags.3299348900.%: "3" tags.3299348900.key: "localkey2" tags.3299348900.propagate_at_launch: "1" tags.3299348900.value: "localvalue2" target_group_arns.#: <computed> vpc_zone_identifier.#: <computed> wait_for_capacity_timeout: "10m" + aws_launch_template.test id: <computed> arn: <computed> default_version: <computed> image_id: "ami-083ebc5a49573896a" instance_type: "t2.micro" latest_version: "0" metadata_options.#: <computed> name: <computed> name_prefix: "test" Plan: 2 to add, 0 to change, 0 to destroy. Do you want to perform these actions? Terraform will perform the actions described above. Only 'yes' will be accepted to approve. Enter a value: yes aws_launch_template.test: Creating... arn: "" => "<computed>" default_version: "" => "<computed>" image_id: "" => "ami-083ebc5a49573896a" instance_type: "" => "t2.micro" latest_version: "" => "<computed>" metadata_options.#: "" => "<computed>" name: "" => "<computed>" name_prefix: "" => "test" aws_launch_template.test: Creation complete after 0s (ID: lt-0d8e6f4f94a683778) aws_autoscaling_group.test: Creating... arn: "" => "<computed>" availability_zones.#: "" => "1" availability_zones.4293815384: "" => "us-east-2a" default_cooldown: "" => "<computed>" desired_capacity: "" => "0" force_delete: "" => "false" health_check_grace_period: "" => "300" health_check_type: "" => "<computed>" launch_template.#: "" => "1" launch_template.0.id: "" => "lt-0d8e6f4f94a683778" launch_template.0.name: "" => "<computed>" launch_template.0.version: "" => "1" load_balancers.#: "" => "<computed>" max_size: "" => "0" metrics_granularity: "" => "1Minute" min_size: "" => "0" name: "" => "<computed>" protect_from_scale_in: "" => "false" service_linked_role_arn: "" => "<computed>" tags.#: "" => "3" tags.2825254636.%: "" => "3" tags.2825254636.key: "" => "localkey1" tags.2825254636.propagate_at_launch: "" => "1" tags.2825254636.value: "" => "localvalue1" tags.2888644505.%: "" => "3" tags.2888644505.key: "" => "resourcekey1" tags.2888644505.propagate_at_launch: "" => "1" tags.2888644505.value: "" => "resourcevalue1" tags.3299348900.%: "" => "3" tags.3299348900.key: "" => "localkey2" tags.3299348900.propagate_at_launch: "" => "1" tags.3299348900.value: "" => "localvalue2" target_group_arns.#: "" => "<computed>" vpc_zone_identifier.#: "" => "<computed>" wait_for_capacity_timeout: "" => "10m" aws_autoscaling_group.test: Creation complete after 2s (ID: tf-asg-20200623194008467200000003) Apply complete! Resources: 2 added, 0 changed, 0 destroyed. Outputs: tags = [ { key = localkey2, propagate_at_launch = 1, value = localvalue2 }, { key = localkey1, propagate_at_launch = 1, value = localvalue1 }, { key = resourcekey1, propagate_at_launch = 1, value = resourcevalue1 } ] $ terraform0.11.14 apply data.aws_ami.test: Refreshing state... data.aws_availability_zones.available: Refreshing state... aws_launch_template.test: Refreshing state... (ID: lt-0d8e6f4f94a683778) aws_autoscaling_group.test: Refreshing state... (ID: tf-asg-20200623194008467200000003) An execution plan has been generated and is shown below. Resource actions are indicated with the following symbols: ~ update in-place Terraform will perform the following actions: ~ aws_autoscaling_group.test tags.2131493069.%: "3" => "0" tags.2131493069.key: "localkey2" => "" tags.2131493069.propagate_at_launch: "true" => "" tags.2131493069.value: "localvalue2" => "" tags.2825254636.%: "0" => "3" tags.2825254636.key: "" => "localkey1" tags.2825254636.propagate_at_launch: "" => "1" tags.2825254636.value: "" => "localvalue1" tags.2888644505.%: "0" => "3" tags.2888644505.key: "" => "resourcekey1" tags.2888644505.propagate_at_launch: "" => "1" tags.2888644505.value: "" => "resourcevalue1" tags.3299348900.%: "0" => "3" tags.3299348900.key: "" => "localkey2" tags.3299348900.propagate_at_launch: "" => "1" tags.3299348900.value: "" => "localvalue2" tags.3593646732.%: "3" => "0" tags.3593646732.key: "localkey1" => "" tags.3593646732.propagate_at_launch: "true" => "" tags.3593646732.value: "localvalue1" => "" tags.3707627218.%: "3" => "0" tags.3707627218.key: "resourcekey1" => "" tags.3707627218.propagate_at_launch: "true" => "" tags.3707627218.value: "resourcevalue1" => "" Plan: 0 to add, 1 to change, 0 to destroy. ``` Building this version of the provider, the difference is no longer present: ```console $ cp ~/go/bin/terraform-provider-aws .terraform/plugins/darwin_amd64/terraform-provider-aws_v2.67.0_x4; terraform0.11.14 init; terraform0.11.14 apply Initializing provider plugins... Terraform has been successfully initialized! You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure. All Terraform commands should now work. If you ever set or change modules or backend configuration for Terraform, rerun this command to reinitialize your working directory. If you forget, other commands will detect it and remind you to do so if necessary. data.aws_availability_zones.available: Refreshing state... data.aws_ami.test: Refreshing state... aws_launch_template.test: Refreshing state... (ID: lt-0d8e6f4f94a683778) aws_autoscaling_group.test: Refreshing state... (ID: tf-asg-20200623194008467200000003) Apply complete! Resources: 0 added, 0 changed, 0 destroyed. Outputs: tags = [ { key = localkey1, propagate_at_launch = 1, value = localvalue1 }, { key = resourcekey1, propagate_at_launch = 1, value = resourcevalue1 }, { key = localkey2, propagate_at_launch = 1, value = localvalue2 } ] ``` Output from acceptance testing (Terraform 0.12 compatible): ``` --- PASS: TestAccAWSAutoScalingGroup_ALB_TargetGroups (176.05s) --- PASS: TestAccAWSAutoScalingGroup_ALB_TargetGroups_ELBCapacity (342.40s) --- PASS: TestAccAWSAutoScalingGroup_autoGeneratedName (89.91s) --- PASS: TestAccAWSAutoScalingGroup_basic (259.25s) --- PASS: TestAccAWSAutoScalingGroup_classicVpcZoneIdentifier (93.45s) --- PASS: TestAccAWSAutoScalingGroup_emptyAvailabilityZones (92.72s) --- PASS: TestAccAWSAutoScalingGroup_enablingMetrics (174.98s) --- PASS: TestAccAWSAutoScalingGroup_initialLifecycleHook (271.36s) --- PASS: TestAccAWSAutoScalingGroup_launchTemplate (62.35s) --- PASS: TestAccAWSAutoScalingGroup_LaunchTemplate_IAMInstanceProfile (61.69s) --- PASS: TestAccAWSAutoScalingGroup_launchTemplate_update (143.24s) --- PASS: TestAccAWSAutoScalingGroup_launchTempPartitionNum (77.30s) --- PASS: TestAccAWSAutoScalingGroup_LoadBalancers (695.77s) --- PASS: TestAccAWSAutoScalingGroup_MaxInstanceLifetime (80.89s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy (108.93s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_InstancesDistribution_OnDemandAllocationStrategy (49.98s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_InstancesDistribution_OnDemandBaseCapacity (82.14s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_InstancesDistribution_OnDemandPercentageAboveBaseCapacity (96.59s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_InstancesDistribution_SpotAllocationStrategy (83.60s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_InstancesDistribution_SpotInstancePools (90.32s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_InstancesDistribution_SpotMaxPrice (112.90s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_InstancesDistribution_UpdateToZeroOnDemandBaseCapacity (73.62s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_LaunchTemplate_LaunchTemplateSpecification_LaunchTemplateName (86.69s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_LaunchTemplate_LaunchTemplateSpecification_Version (85.84s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_LaunchTemplate_Override_InstanceType (85.29s) --- PASS: TestAccAWSAutoScalingGroup_MixedInstancesPolicy_LaunchTemplate_Override_WeightedCapacity (205.06s) --- PASS: TestAccAWSAutoScalingGroup_namePrefix (45.70s) --- PASS: TestAccAWSAutoScalingGroup_serviceLinkedRoleARN (83.67s) --- PASS: TestAccAWSAutoScalingGroup_suspendingProcesses (267.51s) --- PASS: TestAccAWSAutoScalingGroup_tags (299.92s) --- PASS: TestAccAWSAutoScalingGroup_TargetGroupArns (249.92s) --- PASS: TestAccAWSAutoScalingGroup_terminationPolicies (151.45s) --- PASS: TestAccAWSAutoScalingGroup_VpcUpdates (236.40s) --- PASS: TestAccAWSAutoScalingGroup_WithLoadBalancer (389.18s) --- PASS: TestAccAWSAutoScalingGroup_WithLoadBalancer_ToTargetGroup (384.27s) --- PASS: TestAccAWSAutoScalingGroup_withMetrics (96.85s) --- PASS: TestAccAWSAutoScalingGroup_withPlacementGroup (200.69s) ```
|
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
locked and limited conversation to collaborators
Community Note
Terraform Version
Terraform: 0.10.8
AWS Provider: 2.64
Affected Resource(s)
TBD
Terraform Configuration Files
TBD
Debug Output
TBD
Panic Output
Expected Behavior
Terraform should run plan without any issue. Which is the case if provider version 2.63 is used.
Actual Behavior
Terraform quitted with panic as a result of the above log.
Steps to Reproduce
terraform planThe text was updated successfully, but these errors were encountered: