Crash setting up aws_vpc_peering_connection

[rvangraan]

I got this crash while deploying a new aws_vpc_peering_connection resource that uses the outputs of separate modules using Terraform v0.6.3:

resource "aws_vpc_peering_connection" "vpc-peer-pci-core-zone" {
    peer_owner_id = "${var.core-vpc-owner-id}"
    peer_vpc_id = "${module.core.core-zone-vpc-id}"
    vpc_id = "${module.pci.pci-zone-vpc-id}"
    auto_accept = true
}

Edit from @catsby: moved crash log to https://gist.github.com/catsby/a4dfde333e8bb540f019

[rvangraan]

It looks like the peering connection got created, but then something went haywire.

[rvangraan]

This has to do with

    auto_accept = true

when I removed it, the crash disappeared.

[apparentlymart]

Thanks for the report and the debugging effort, @rvangraan.

Looks like this is failing trying to dereference one of the AcceptVpcPeeringConnectionInput response fields:

terraform/builtin/providers/aws/resource_aws_vpc_peering_connection.go

Line 131 in 0c2f189

return *pc.Status.Code, err

Not familiar at all with this API, so no strong theories yet. Just wondering, though: were you trying to peer between two VPCs in the same AWS account, or across two accounts?

[dsalazar-carecloud]

I experienced the same issue. And in my scenario it was across two accounts. I'm assuming that it has to do with the inability to prove that you are the owner of that other account and execute the auto acceptance of the peer request of the account vpc you're trying to peer in to within the context of the run.

[rvangraan]

@apparentlymart: This was with two VPCs on the same account.

[catsby]

Hello –

I wasn't able to reproduce this directly, but I did open and merge #3490 to add better error handling and check for nil references.

Please let me know if you're still hitting this.
Thanks!

[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.