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

Bug Report Deployment template validation fails when selecting Virtual WAN and single subscription #1470

Closed
ahammond-dev opened this issue Nov 9, 2023 · 3 comments · Fixed by #1472
Assignees
Labels
bug Something isn't working

Comments

@ahammond-dev
Copy link

Describe the bug
When selecting a Single Platform Subscription and Virtual WAN as the network topology the following error is produced when reaching the Review + Create page. This occurs whether routing intent is enabled or not. This does not occur when selecting another network topology such as hub and spoke. It also does not occur when selecting dedicated platform subscriptions.

{"code":"InvalidTemplate","message":"Deployment template validation failed: 'The value for the template parameter 'enablevWANRoutingIntent' at line '109' and column '35' is not provided. Please see https://aka.ms/arm-create-parameter-file for usage details.'."}

Steps to reproduce

  1. Begin the deployment by clicking the "Deploy to Azure" Link on https://github.com/Azure/Enterprise-Scale#deploying-enterprise-scale-architecture-in-your-own-environment
  2. On the Azure Core Setup page, select "single" under Platform subscription options.
  3. On the Network topology and connectivity page, select "Virtual WAN (Microsoft managed)" under Deploy networking topology.
  4. All other settings can remain as the defaults.

Screenshots
image

@ahammond-dev ahammond-dev added the bug Something isn't working label Nov 9, 2023
@jtracey93
Copy link
Collaborator

Thanks for reporting @rozkurt can you take a look and investigate this please and come back to this thread here and @ahammond-dev 👍

@rozkurt
Copy link
Contributor

rozkurt commented Nov 9, 2023

@ahammond-dev @jtracey93 I reviewed the code and just noticed what causing this issue. I'm currently testing the fix and hoping that it would be merged and be available early next week!

@rozkurt
Copy link
Contributor

rozkurt commented Nov 14, 2023

@ahammond-dev The fix has been applied, tested and merged into the main branch now. Please test it if possible and let us know if you notice any other issues. Thank you once again for reporting it!

CC: @jtracey93

@jtracey93 jtracey93 linked a pull request Nov 14, 2023 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants