Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retry support for azurerm_virtual_network_peering #3392

Merged
merged 1 commit into from May 7, 2019

Conversation

tiwood
Copy link
Contributor

@tiwood tiwood commented May 7, 2019

This PR introduces retry support (Create/Update) for azurerm_virtual_network_peering.

This is required as sometimes one of the virtual networks involved in the peering is not completely provisioned (just created or just updated), in which case the following error is returned from the API:

{
	"error": {
		"code": "ReferencedResourceNotProvisioned",
		"message": "Cannot proceed with operation because resource /subscriptions/subscriptionId/resourceGroups/resourceGroupName/providers/Microsoft.Network/virtualNetworks/vNetName used by resource /subscriptions/subscriptionId/resourceGroups/resourceGroupName/providers/Microsoft.Network/virtualNetworks/virtualNetworkName/virtualNetworkPeerings/vnetPeeringName is not in Succeeded state. Resource is in Updating state and the last operation that updated/is updating the resource is PutSubnetOperation.",
		"details": []
	}
}

This fixes #2605

Copy link
Member

@tombuildsstuff tombuildsstuff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hey @tiwood

Thanks for this PR - this LGTM 👍

@tombuildsstuff tombuildsstuff added this to the v1.28.0 milestone May 7, 2019
@tombuildsstuff
Copy link
Member

Tests pass:

Screenshot 2019-05-07 at 12 31 43

@tombuildsstuff tombuildsstuff merged commit 4da4aa7 into hashicorp:master May 7, 2019
tombuildsstuff added a commit that referenced this pull request May 7, 2019
@tiwood tiwood deleted the retry-vnet-peering branch May 7, 2019 19:44
@ghost
Copy link

ghost commented May 17, 2019

This has been released in version 1.28.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
	version = "~> 1.28.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Jun 7, 2019

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. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Jun 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Concurrently peering vnets and adding subnets to them fails
2 participants