Terraform crash when adding aws_route53_record

[ultra70]

Terraform Version

0.7.1

Affected Resource(s)

aws_route53_record

Terraform Configuration Files

https://gist.github.com/ultra70/9f4cf53478dcf506a956577928ea3d9b

Debug Output

https://gist.github.com/ultra70/8a3164f9e7342053562bd0815dd0da3c

Panic Output

https://gist.github.com/ultra70/1a538ab2fe903474673712b7b9a7f563

Expected Behavior

aws_route53_record.m1_txt created in AWS Route53

Actual Behavior

Nothing happened on the AWS side.

Steps to Reproduce

Add a . to the end of name = "m1._domainkey" in resource "aws_route53_record" "m1_txt" then run terraform apply

Important Factoids

None

References

None

[stack72]

Hi @ultra70

Sorry this has caused you problems - this is actually something we have already fixed as part of Terraform 0.7.2 #8399

FYI, lines from the crash:

2016/08/31 22:12:58 [DEBUG] plugin: terraform: panic: interface conversion: interface {} is nil, not *route53.ChangeResourceRecordSetsOutput
2016/08/31 22:12:58 [DEBUG] plugin: terraform: 
2016/08/31 22:12:58 [DEBUG] plugin: terraform: goroutine 455 [running]:
2016/08/31 22:12:58 [DEBUG] plugin: terraform: panic(0x2846ac0, 0xc4206e2c40)
2016/08/31 22:12:58 [DEBUG] plugin: terraform:  /opt/go/src/runtime/panic.go:500 +0x1a1
2016/08/31 22:12:58 [DEBUG] plugin: terraform: github.com/hashicorp/terraform/builtin/providers/aws.resourceAwsRoute53RecordCreate(0xc42052d0e0, 0x2534d60, 0xc4200669a0, 0x284bcc0, 0x414ab1)
2016/08/31 22:12:58 [DEBUG] plugin: terraform:  /opt/gopath/src/github.com/hashicorp/terraform/builtin/providers/aws/resource_aws_route53_record.go:274 +0xb0a
2016/08/31 22:12:58 [DEBUG] plugin: terraform: github.com/hashicorp/terraform/helper/schema.(*Resource).Apply(0xc4203811a0, 0xc4206fa480, 0xc42057bd80, 0x2534d60, 0xc4200669a0, 0x1, 0xc4201f7140, 0x0)

Hope this helps

Paul

[ultra70]

Thanks stack72, I'll update and try again.

[ultra70]

Looking good, thank you.

[stack72]

👍

[ghost]

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.