-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
[Network] Eventual Consistency Bug in the Virtual Network Gateway API #1233
Comments
@DeepakRajendranMsft could you please take a look and help re-route the issue as appropriate? thanks! |
👋 hey @DeepakRajendranMsft @veronicagg - is there any update on this? :) |
@Nilambari @lamchester please take a look |
Hey @DeepakRajendranMsft / @Nilambari / @lamchester Just an FYI that I've opened a bug this morning about a similar issue with Redis on the Internal Network - which seems like it might be related: #1347 Is there any update on this? :) Thanks! |
@DeepakRajendranMsft to assign to @Nilambari @lamchester |
👋 hey @Nilambari @lamchester Is there any update on this issue, or a rough timeframe for when this issue would be fixed? Thanks! |
Hey, We acknowledge the issue and we will work on getting the estimates required to fix this issue. We will get back with the release dates for the fix. |
Awesome, thanks @MohitGargVpn! |
Many thanks @MohitGargVpn |
Hey @MohitGargVpn Did you manage to work out a rough timeframe for this issue in the end? :) Thanks! |
We will fix and release the patch by 9/15/17. Thanks for reporting the issue. |
The fix is already checked in and still on-track for 9/15 |
Hey @MohitGargVpn @dominik-lekse has run the acceptance tests (which create and tear down a Virtual Network Gateway) and it appears we're still seeing issues on deletion, as such I just wanted to confirm if this fix has been released yet? Thanks! |
The fix is in rollout and has gone to many regions but not all. Please try it again after a week or so. BTW which region did you try and on which date? I can check if that region had the fix or not? If you could also give me subscriptionId, and VNET URI i can investigate why vnet/subnet deletion failed for you. |
@MohitGargVpn has this finished rolling out yet? I've just tried running this in West Europe and we're still seeing this issue:
Thanks! |
@MohitGargVpn I also tried this in the region West Europe on Monday without success. Could you reference a region in which the fix has been rolled out already? |
ping @MohitGargVpn :) |
Is this good to go? |
@veronicagg would you mind seeing if there's an update here? Thanks! :) |
The first fix was rolled out on 9/15. The original race condition was fixed. But we identified one more race condition which can lead to same behavior. The fix for that is planned to be rolled out by 11/15. |
@MohitGargVpn thanks for the update. Once this has been rolled out - would you be able to tell us a region for us to test and confirm against? Thanks! |
Sure. I will update here with the region info. |
@MohitGargVpn, any update on this? |
As a side remark on this issue: The Azure portal gets tricked into this one as well. If the user is too quick in deleting the subnet after deleting the vnet gateway, an error appears in the notifications. |
@MohitGargVpn When I test the application gateway, I hit a similar issue hashicorp/terraform-provider-azurerm#488. I was using terraform to build a CI, and the failure rate is pretty high because of this issue.
|
@MohitGargVpn - updates? thanks |
@MohitGargVpn common, half of year to fix issue. |
ping @MohitGargVpn - is there any update available for this issue? :) |
@tombuildsstuff Are there plans for this provider to delete the resource group instead of (or in addition to) the individual resources? If there is another issue/thread with that answer, would you direct me to it?
|
@MohitGargVpn - updates? |
This should now be fixed for all the regions. Can you please try it out? |
@MohitGargVpn from what I can see, the bugs in the API appear to have been fixed. The one remaining error is a Thanks! |
@MohitGargVpn I've spent a little while validating this and can confirm that this appears to be fixed :) As such we've just merged support for Virtual Network Gateways into Terraform - and I'm going to close this issue. Thanks! |
Hey @tombuildsstuff. We tried to bring back testing our azure templates but are back to seeing this error every time.
|
👋 Hey y'all
@pmcatominey and @dominik-lekse have been investigating adding support for Virtual Network Gateway's using the Azure SDK for Go - which has led to the PR's hashicorp/terraform#9255 and hashicorp/terraform#13886
Whilst adding support, they've identified an eventual consistency bug in the API where deleting a Virtual Network Gateway completes successfully (and returns a 404 when attempting to retrieve it), but the resource still exists, which prevents the Subnet from being deleted.
Whilst there's several workarounds we could implement - this isn't an ideal for several reasons:
Would it be possible for someone from the Networking team to look into this issue?
Thanks!
cc @DeepakRajendranMsft / @Nilambari
The text was updated successfully, but these errors were encountered: