web 2022-09-01 - API requires vnetRouteAllEnabled be set in both siteProperties and siteConfig

[jackofallops]

Both values must be set in order to successfully submit a request, this shouldn't need to be set in two places? Should one of these be deprecated or take priority?

StatusCode=400 -- Original Error: Code="BadRequest"
Message="There was a conflict. VnetRouteAllEnabled has diffirent values as
site property and site config"

NB: There's also a typo in error message.

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @antcp, @AzureAppServiceCLI.

Issue Details

---

Both values must be set in order to successfully submit a request, this shouldn't need to be set in two places? Should one of these be deprecated or take priority?

StatusCode=400 -- Original Error: Code="BadRequest"
Message="There was a conflict. VnetRouteAllEnabled has diffirent values as
site property and site config"

NB: There's also a typo in error message.

Author:	jackofallops
Assignees:	-
Labels:	question, App Services, Service Attention, customer-reported
Milestone:	-

[navba-MSFT]

Adding service team to look into this.

[SwintDC]

We are having the same issue with an App Service where vnetRouteAllEnabled is turned off. When running the Azure CLI command "az webapp vnet-integration add" for a newly created staging slot (created with --configuration-source $appServiceName), then we get the following error:
ERROR: There was a conflict. VnetRouteAllEnabled has different values as site property and site config OperationStopped: Integrating staging slot in vnet failed.

The Azure CLI has version 2.50.0, it also failed with version 2.49.0.

We found a temporary workaround though: turning on vnetRouteAllEnabled on the App Service before creating the staging slot fixes this.

Is there any progress on this issue?

[piotrgradzinski]

Any update on this issue? I'm having same problem with fresh web app, without slots, freshly created without anything deployed.

I'm using newest az cli (2.52.0):

az webapp vnet-integration add --name="APP_NAME" --resource-group="RESOURCE_GROUP_NAME" --vnet="VNET_NAME" --subnet="SUBNET_NAME"

that results in:

There was a conflict. VnetRouteAllEnabled has different values as site property and site config

[mrk9676]

Hello all,

We are getting below issue since last 2 days for Azure App Service VNET configuration. It's behaving very odd. Enabling vnet_route_all_enabled is throwing the conflict. If I remove this setting, VNET Routing is getting enabled by default in few subscriptions. In few subscriptions it is not enabling. Please let me know if there is any solution or workaround.

Error:: Code="BadRequest" Message="There was a conflict. SiteConfig.VnetRouteAllEnabled cannot be modified. Please modify the Site.VnetRouteAllEnabled property."

[mtsuggs]

This has also started happening within our environment sporadically. This happens in some environments and not in others, and happens for some pipelines and not others. We have 30+ micro services that are all deployed the same way, and yet some have isuses some do not. The build error is: ##[error]undefined: There was a conflict. SiteConfig.VnetRouteAllEnabled cannot be modified. Please modify the Site.VnetRouteAllEnabled property.

I have confirmed the env setting on both staging slot and live set is already set to 1.

[mrk9676]

This has also started happening within our environment sporadically. This happens in some environments and not in others, and happens for some pipelines and not others. We have 30+ micro services that are all deployed the same way, and yet some have isuses some do not. The build error is: ##[error]undefined: There was a conflict. SiteConfig.VnetRouteAllEnabled cannot be modified. Please modify the Site.VnetRouteAllEnabled property.

I have confirmed the env setting on both staging slot and live set is already set to 1.

True, it is very odd to see. We are also experiencing the same.

[mtsuggs]

The fix is what it says, move the node from. The site config to the parent under properties.

…

On Thu, May 2, 2024, 1:15 PM Ram Manyam ***@***.***> wrote: This has also started happening within our environment sporadically. This happens in some environments and not in others, and happens for some pipelines and not others. We have 30+ micro services that are all deployed the same way, and yet some have isuses some do not. The build error is: ##[error]undefined: There was a conflict. SiteConfig.VnetRouteAllEnabled cannot be modified. Please modify the Site.VnetRouteAllEnabled property. I have confirmed the env setting on both staging slot and live set is already set to 1. True, it is very odd to see. We are also experiencing the same. — Reply to this email directly, view it on GitHub <#24681 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACLE5PFJBXIC7N42K4KU2TTZAJ7CLAVCNFSM6AAAAAAZ4MWGPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJRGIYDMOJQGQ> . You are receiving this because you commented.Message ID: ***@***.***>