Closed Fryyyyy closed 9 months ago
I've updated the VM sizing API to use a new one that give us the Premium Storage availability flag
azure.core.exceptions.ResourceExistsError: (OperationNotAllowed) Operation could not be completed as it results in exceeding approved standardBasv2Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: eastus, Current Limit: 0, Current Usage: 0, Additional Required: 4, (Minimum) New Limit Required: 4. Submit a request for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%22****%22,%22command%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22eastus%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardBasv2Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:4,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardBasv2Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests
azure.core.exceptions.HttpResponseError: (InvalidParameter) Requested operation cannot be performed because the VM size Standard_F4 does not support the storage account type Premium_LRS of disk 'evidence_jenkins_libcloudforensics_e2e_data_disk_snapshot_19dd1340_copy'. Consider updating the VM to a size that supports Premium storage.