[Network/VPNGateway] deployment operation failed due to an intermittent error
#21164
Comments
ghost
added
the
needs-triage
JackTn
added
Network - VPN Gateway
Service Attention
ghost
removed
the
needs-triage
|
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @vpngwsuppgithub. Issue DetailsBriefVPN gateway deployment keeps failing with helpless information DescriptionWhen creating a virtual network gateway for VPN Type with route-based policy, the create operation returns with server-side error without debugging/helpful information to investigate. I have tried with different SKU types and modified the customeRoute prefix value, which makes no different and all failed. related API:examplegateway request payload {
"location": "eastus",
"properties": {
"activeActive": false,
"customRoutes": {
"addressPrefixes": [
"101.168.0.6/32"
]
},
"enableBgp": false,
"enablePrivateIpAddress": true,
"gatewayType": "Vpn",
"ipConfigurations": [
{
"name": "vnetGatewayConfig",
"properties": {
"privateIPAllocationMethod": "Dynamic",
"publicIPAddress": {
"id": "/subscriptions/xxx-xxxx/resourceGroups/xxx-rg/providers/Microsoft.Network/publicIPAddresses/vpnpubip001"
},
"subnet": {
"id": "/subscriptions/xxx-xxxx/resourceGroups/xxx-rg/providers/Microsoft.Network/virtualNetworks/vpngw001/subnets/GatewaySubnet"
}
}
}
],
"sku": {
"name": "VpnGw3AZ",
"tier": "VpnGw3AZ"
},
"vpnType": "RouteBased"
}
}reponse error message: {
"error": {
"code": "VmssGatewayDeploymentFailed",
"details": [],
"message": "The gateway deployment operation failed due to an intermittent error. Please try again."
},
"status": "Failed"
}
|
|
Hi, i'm also trying to create VNG and face same issue , any update on this ? |
|
Hi, |
|
Same here - West Europe. Please fix! |
|
Same here - UKSouth and UKWest, tried with VpnGw1 & VpnGw1AZ, interestingly the basic SKU seems to work ok, but that's not what I need. |
|
The same is for uswest3 with VpnGw1 & VpnGw2. Basic doesn't work as well |
|
Same thing here - for west Europe as well. |
Same here - trying the same in West Europe - any luck on the support ticket side? |
|
Same issue here. Happening in West Europe trying to deploy a VpnGw2AZ. Tried deployment via Terraform and the Portal. |
|
Note there is an issue currently with Azure Key Vault that may be causing this problem - if you look in the Service Health page there is an alert there that is affecting downstream Azure services like VPN Gateway. |
|
From Azure support: Thank you for contacting Microsoft Azure Networking support. Please know that we are currently investigating an ongoing global issue regarding Virtual Network Gateway (VPN Gateway) deployments and we will get back to you with updates once this has been mitigated.” Seems the key vault issue is wiping out network services. The status website need to reflect this and not just list key vault as impacted |
|
Hello, Indeed joining the list to report an issue, neither the empty PUT request is helping
|
|
Same issue here... This has been happening all day. |
|
Yesterday I bought a subscription and created a fresh virtual network in southeast asia. Status: Conflict |
|
After this confirmation at 3rd Nov @ 05:52 UTC https://status.azure.com/en-us/status/history/ I was able to provision VpnGw1 in UKSouth this morning. |
|
Seems to be mitigated. Can also deploy the VGW now. |
|
Got an answer from the support team.
EDIT: My deployment succeeded this morning in Region West Europe for a VpnGw1 Route based ! I'll let you know if I have some updates from support, but indeed this seems to be mitigated. |
|
Indeed it works on Express route gateways as well West Europe. |
|
Confirmed creation of VpnGw1 in west us 3 |
|
Hi, |
|
This issue seems to be current again. We're currently unable to deploy any VPN gateway to any subscription or any tenant. No mentions of this on the service health pages. So, curious as to what's causing it this time. |
|
Yeah, for the past three days, we've been facing the same issue in our organization. The deployment has failed multiple times, even after many retries. Unfortunately, Microsoft support wasn't helpful. We're still trying to deploy this resource, but it continues to fail. |
|
Also a problem on my side. tried it since 09 of January. Region West Europe with SKU VPNGw2
|
|
@soufianerabi @tanarchytan, I tried deploying in north europe last friday (jan. 12th, 2024), which completes successfully, which makes me believe Microsoft simply has some serious resource issues in the west europe region. It's not the first time (or sign of) this is happening, a few months back we were unable to roll out other resources (VM's, VMSS'es (for AKS)) because apparently the resource was unavailable in a specific zone in west europe. Would be helpful if Microsoft would simply clarify the current state of west europe, if there's a capacity issue, that's annoying, but I'd rather have them tell us then having to find out this way... |
|
Some here, VPN deploy in West Europe: |
|
Me too |
|
Microsoft is not good, there are problems all the time. That's horrible |
|
Currently facing same issue in West Europe for VpnGw1 and VpnGw1AZ |
|
Me too |
|
Microsoft have called me to say that they are not sure what the issue is and it could be months before it is resolved. The attached states capacity constraints but still no resolution in site just a warning set up to say capacity constraints wont allow you to build gateways in west europe for the foreseeable. |
|
@lgriffithsdoherty , thank you for sharing this! :) I hope Microsoft makes quick work of expanding their capacity in west europe :/ |
|
This is a serious blocking issue for us as well, that will possibly postponed our go-live date. I tried to move only the vnet and vpn gateway to a different region but without success, possible we will need to move all network related resources or the entire infrastructure to a different region. For now we are using a bastion VM but that is not a cheap solution as on one VM only two people can work simultaneously. Looks like Microsoft doesn't care much about this problem. |
|
@atovivan Instead of moving the VNet, you might want to try creating a second VNet for just the VPN, then peer that VNet with the 'original' VNet, that should work? (otherwise, perhaps a custom solution with a VM + custom VPN software (like wireguard) could work for your needs? However crappy that is, it might be 'a way out') |
|
Cannot believe this is happening and even that Microsoft says it could be months before it is resolved. Another question is: is this an intermitent error and perhaps if I'm lucky I will get my VPN deployed, or does it fail every time? |
|
@efcorpa FWIW I tried deploying every SKU multiple times yesterday and it failed every single time. |
|
@efcorpa I've the same issue by different customers, the only one option is to make a resource group with a vpn gateway and a vnet in a other region and make a peer between your current vnet and the one that is deployed in a other region. If you have questions let me know |
|
The problem unfortunately still exists 👎 |
|
I have been retrying every day for a few weeks at this point, and only just today was I able to succesfully deploy a VPN Gateway to westeurope, with the SKU |
Probably just enough people gave up on westeurope and picked a different region. We moved everything to Sweden central, not being able to reliably deploy things is not an risk we're willing to take. |
|
Over a year later and this issue still persists. At a minimum it'd be nice if it was capacity issues that this is reflected in the error message. |
|
Hi @MarkTallentire, are you still experiencing this issue in West Europe region? the capacity issue should have been resolved already. |
|
Hi @wuxu92
Yes, still seem to be getting this in West Europe and North Europe.
I was able to succesfully make one in UK South but our clients require us to have all our infrastructure in Europe
…On Tue, 19 Mar 2024 at 04:43, Xu Wu ***@***.***> wrote:
Hi @MarkTallentire <https://github.com/MarkTallentire>, are you still
experiencing this issue in West Europe region? the capacity issue should
have been resolved already.
—
Reply to this email directly, view it on GitHub
<#21164 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGIAYPSL4A3OZ3XN5KIUJ7DYY667HAVCNFSM6AAAAAARH366NGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBVG42TAOJXG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
same problem in West Europe for VPNGw2 |
and others
Brief
VPN gateway deployment keeps failing with helpless information
Description
When creating a virtual network gateway for VPN Type with route-based policy, the create operation returns with server-side error without debugging/helpful information to investigate. I have tried with different SKU types and modified the customeRoute prefix value, which makes no different and all failed.
related API:
azure-rest-api-specs/specification/network/resource-manager/Microsoft.Network/stable/2021-08-01/virtualNetworkGateway.json
Line 1937 in ae227e2
example
gateway request payload
{ "location": "eastus", "properties": { "activeActive": false, "customRoutes": { "addressPrefixes": [ "101.168.0.6/32" ] }, "enableBgp": false, "enablePrivateIpAddress": true, "gatewayType": "Vpn", "ipConfigurations": [ { "name": "vnetGatewayConfig", "properties": { "privateIPAllocationMethod": "Dynamic", "publicIPAddress": { "id": "/subscriptions/xxx-xxxx/resourceGroups/xxx-rg/providers/Microsoft.Network/publicIPAddresses/vpnpubip001" }, "subnet": { "id": "/subscriptions/xxx-xxxx/resourceGroups/xxx-rg/providers/Microsoft.Network/virtualNetworks/vpngw001/subnets/GatewaySubnet" } } } ], "sku": { "name": "VpnGw3AZ", "tier": "VpnGw3AZ" }, "vpnType": "RouteBased" } }reponse error message:
{ "error": { "code": "VmssGatewayDeploymentFailed", "details": [], "message": "The gateway deployment operation failed due to an intermittent error. Please try again." }, "status": "Failed" }The text was updated successfully, but these errors were encountered: