Closed potejasw closed 3 months ago
@potejasw Could you do a git pull and try again?
We just merged this enhancement: https://github.com/microsoft/azure_arc/pull/2573
I tested locally using the following conditions:
Triggering the deployment went fine when using the updated logic:
@janegilring I will check on this and update you.
@janegilring We have passed the stage of tenant issue and we are stuck with number CPU's in eastUS region are seeing less when customer execute the command. With other region also customer sees less CPUs. But when I execute at my laptop it shows normal.
Current error we are getting is “There is not enough VM capacity in the eastus region to deploy the Jumpstart environment”. Checking other regions in the same geography with enough capacity (32 cores)
Output when I executed from my machine.
PS C:\Users\Username> az vm list-usage --location EastUS --output table --query "[].{Name:localName, Current:currentValue, Limit:limit, Unit:unit, Status:status}" Name Current Limit
Availability Sets 0 2500 Total Regional vCPUs 64 100 Virtual Machines 2 25000 Virtual Machine Scale Sets 0 2500 Dedicated vCPUs 0 3000 Cloud Services 0 2500 Total Regional Low-priority vCPUs 0 100 Standard ESv5 Family vCPUs 64 100
Customer needs to increase their vCPU quota. They are showing a limit of 20 regional vCPU. This is an issue with the vCPU quota on the targeted subscription.
Thank you for your response. I will share the same with customer and update you.
The customer has tried, but failed. Could you please share the steps to increase the vCPU counts on the subscription
@potejasw In the Azure portal, go the subscription targeted for HCIBox deployment, select Usage + Quotas
, select Provider:Compute
, select the target Azure region and request increasing the relevant quotas by clicking the button in the column Adjustable
:
Thank you for your update and the screenshot. I will share the same with customer and share you the results
@potejasw Any updates or are we good to close this issue?
I apologise for not responding to this thread. The issue has been resolved. You can go ahead and close the case.
No worries, thanks for the update.
Is your issue related to a Jumpstart scenario, HCIBox?
https://arcjumpstart.com/azure_jumpstart_hcibox/deployment_azd
Describe the issue or the bug
To Reproduce
Expected behavior
Environment summary
Have you looked at the Troubleshooting and Logs section? <!Its in the initial stage of creating RG
Screenshots
Additional context