You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the issue or the bug
Configure-AKSWorkloadCluster.ps1 (line 25) and Configure-VMLogicalNetwork.ps1 (line 20) use hard coded locations/regions. If HCIBox is provisioned into supported region other than East US (e.g. West Europe), Azure resources in these scripts are provisioned into a different region.
Expected behavior
All resources within this solution should be provisioned into same region. Either change code so that it takes location from Resource Group location (would it be $location = $env:resourceGroup.location ?) or alternatively modify documentation so that user is instructed to modify location in each file manually. This is already done for Configure-AKSWorkloadCluster.ps1 instructions for modifying $groupObjectID. However, it'd be better not to use hard coded locations in the first place.
Have you looked at the Troubleshooting and Logs section?
Yes
Screenshots
Additional context
The text was updated successfully, but these errors were encountered:
Hi mikaseitsonen! Thank you for opening this issue. We appreciate your contribution and welcome you to our community! We are glad to have you here and to have your input on the Arc Jumpstart.
Is your issue related to a Jumpstart scenario, ArcBox, HCIBox, or Agora?
https://arcjumpstart.com/azure_jumpstart_hcibox/AKS and https://arcjumpstart.com/azure_jumpstart_hcibox/RB
Describe the issue or the bug
Configure-AKSWorkloadCluster.ps1 (line 25) and Configure-VMLogicalNetwork.ps1 (line 20) use hard coded locations/regions. If HCIBox is provisioned into supported region other than East US (e.g. West Europe), Azure resources in these scripts are provisioned into a different region.
Expected behavior
All resources within this solution should be provisioned into same region. Either change code so that it takes location from Resource Group location (would it be $location = $env:resourceGroup.location ?) or alternatively modify documentation so that user is instructed to modify location in each file manually. This is already done for Configure-AKSWorkloadCluster.ps1 instructions for modifying $groupObjectID. However, it'd be better not to use hard coded locations in the first place.
Have you looked at the Troubleshooting and Logs section?
Yes
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: