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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃 Bug Report - vWan connectivity module failing with Network.DNS.EnableProxy error #334

Closed
jfaurskov opened this issue Oct 10, 2022 · 0 comments 路 Fixed by #335
Closed
Assignees
Labels
Area: Networking bug Something isn't working

Comments

@jfaurskov
Copy link
Contributor

Describe the bug

When deploying the vwanconnectivity module the deployment fails with the following error. {"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"InvalidParameter","message":"The value '(Network.DNS.EnableProxy)' is an invalid value for this parameter."}]}. This is related to the Azure Firewall deployment.

To Reproduce

Steps to reproduce the behaviour:

  1. Deploy vwanConnectivity module as described here

Expected behaviour

vWan and related artifacts deployed successfully.

Screenshots 馃摲

N/A

Correlation ID

N/A

Additional context

This seems to be caused by the following lines in vwanconnectivity.bicep 馃憤
additionalProperties: {
'Network.DNS.EnableProxy': '${parAzFirewallDnsProxyEnabled}'
}
Once removed this error no longer occurs. The lines are not present in the hubNetowrking.bicep module either.

@jfaurskov jfaurskov added the bug Something isn't working label Oct 10, 2022
@ghost ghost added the Needs: Triage 馃攳 Needs triaging by the team label Oct 10, 2022
@jfaurskov jfaurskov changed the title 馃 Bug Report - PLEASE CHANGE ME TO SOMETHING DESCRIPTIVE 馃 Bug Report - vWan connectivity module failing with Network.DNS.EnableProxy error Oct 10, 2022
@jfaurskov jfaurskov linked a pull request Oct 10, 2022 that will close this issue
10 tasks
@jtracey93 jtracey93 added Area: Networking and removed Needs: Triage 馃攳 Needs triaging by the team labels Oct 10, 2022
jtracey93 pushed a commit that referenced this issue Oct 10, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Nov 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Area: Networking bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants