[英]Deployment of Bicep fails on Visual Studio Code - Unexpected character encountered while parsing value: r. Path ''
[英]Azure Storage Accounts bicep deployment fails for sku Standard_LRS
我在Standard_LRS
上有以下用於 Azure Blob 存儲的二頭肌文件
resource storageAccount 'Microsoft.Storage/storageAccounts@2022-05-01' = {
name: 'ifmsstorageaccount'
location: location
sku: {
name: 'Standard_LRS'
}
kind: 'BlockBlobStorage'
properties: {
accessTier: 'Hot'
}
}
部署到 azure 時出現以下錯誤:
ERROR: ***"status":"Failed","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":"Conflict","message":"***\r\n
\"status\": \"Failed\",\r\n \"error\": ***\r\n \"code\":
\"ResourceDeploymentFailure\",\r\n \"message\": \"The resource
operation completed with terminal provisioning state 'Failed'.\",\r\n
\"details\": [\r\n ***\r\n \"code\": \"DeploymentFailed
\",\r\n \"message\": \"At least one resource deployment operation
failed. Please list deployment operations for details. Please see
https://aka.ms/DeployOperations for usage details.\",\r\n
\"details\": [\r\n ***\r\n \"code\": \"BadRequest
\",\r\n \"message\": \"***\\r\\n \\\"error\\\": ***\\r\\n
\\\"code\\\": \\\"InvalidParameter\\\",\\r\\n \\\"message\\\": \\\"Pricing tier doesn't match the subscription's billing model. Read
http://aka.ms/PricingTierWarning for more details. Operation Id:
'ccfd950570ed8ac1dd3214b811d46933'\\\"\\r\\n ***\\r\\n***\"\r\n
***\r\n ]\r\n ***\r\n ]\r\n ***\r\n***"***,***"code":"Conflict","message":"***\r\n \"status\":
\"Failed\",\r\n \"error\": ***\r\n \"code\":
\"ResourceDeploymentFailure\",\r\n \"message\": \"The resource
operation completed with terminal provisioning state 'Failed'.\",\r\n
\"details\": [\r\n ***\r\n \"code\": \"DeploymentFailed
\",\r\n \"message\": \"At least one resource deployment operation
failed. Please list deployment operations for details. Please see
https://aka.ms/DeployOperations for usage details.\",\r\n
\"details\": [\r\n ***\r\n \"code\": \"BadRequest
\",\r\n \"message\": \"***\\r\\n \\\"error\\\": ***\\r\\n
\\\"code\\\": \\\"ParameterOutOfRange\\\",\\r\\n \\\"message\\\":
\\\"The value of the 'Sku.Name' should be in: [Standard_B1ms,
Standard_B1s, Standard_B2s, Standard_B4ms, Standard_B8ms,
Standard_D16s_v3, Standard_D2s_v3, Standard_D32s_v3, Standard_D4s_v3,
Standard_D64s_v3, Standard_D8s_v3, Standard_E16s_v3, Standard_E2s_v3,
Standard_E32s_v3, Standard_E4s_v3, Standard_E64s_v3, Standard_E8s_v3,
Standard_M128ms, Standard_M128s, Standard_M64ms, Standard_M64s,
Standard_E48s_v3, Standard_D2ds_v4, Standard_D4ds_v4, Standard_D8ds_v4,
Standard_D16ds_v4, Standard_D32ds_v4, Standard_D48ds_v4,
Standard_D64ds_v4, Standard_E2ds_v4, Standard_E4ds_v4, Standard_E8ds_v4,
Standard_E16ds_v4, Standard_E32ds_v4, Standard_E48ds_v4,
Standard_E64ds_v4, Standard_D48s_v3, Standard_E20ds_v4, Standard_M8ms,
Standard_M16ms, Standard_M32ts, Standard_M32ls, Standard_M32ms,
Standard_M64ls, Standard_M64, Standard_M64m, Standard_M128, Standard_M128m, Standard_B12ms, Standard_B16ms, Standard_B20ms,
Standard_D2ads_v5, Standard_D4ads_v5, Standard_D8ads_v5,
Standard_D16ads_v5, Standard_D32ads_v5, Standard_D48ads_v5,
Standard_D64ads_v5, Standard_D96ads_v5, Standard_E2ads_v5,
Standard_E4ads_v5, Standard_E16ads_v5, Standard_E20ads_v5,
Standard_E32ads_v5, Standard_E48ads_v5, Standard_E64ads_v5,
Standard_E96ads_v5, Standard_D2_v5, Standard_D4_v5, Standard_D8_v5,
Standard_D16_v5, Standard_D32_v5, Standard_D48_v5, Standard_D64_v5,
Standard_D96_v5, Standard_D2s_v5, Standard_D4s_v5, Standard_D8s_v5,
Standard_D16s_v5, Standard_D32s_v5, Standard_D48s_v5, Standard_D64s_v5,
Standard_D96s_v5, Standard_D2ds_v5, Standard_D4ds_v5, Standard_D8ds_v5,
Standard_D16ds_v5, Standard_D32ds_v5, Standard_D48ds_v5,
Standard_D64ds_v5, Standard_D96ds_v5, Standard_E2ds_v5,
Standard_E4ds_v5, Standard_E8ds_v5, Standard_E16ds_v5,
Standard_E20ds_v5, Standard_E32ds_v5, Standard_E48ds_v5,
Standard_E64ds_v5, Standard_E96ds_v5, Standard_E104ids_v5,
Standard_E2bds_v5, Standard_E4bds_v5, Standard_E8bds_v5,
Standard_E16bds_v5, Standard_E32bds_v5, Standard_E48bds_v5,
Standard_E64bds_v5]. Verify that the specified parameter value is
correct.\\\"\\r\\n ***\\r\\n***\"\r\n ***\r\n ]\r\n
***\r\n ]\r\n ***\r\n***"***,***"code":"Conflict","message":"***\r\n
\"status\": \"Failed\",\r\n \"error\": ***\r\n \"code\":
\"ResourceDeploymentFailure\",\r\n \"message\": \"The resource
operation completed with terminal provisioning state 'Failed'.\",\r\n
\"details\": [\r\n ***\r\n \"code\": \"DeploymentFailed
\",\r\n \"message\": \"At least one resource deployment operation
failed. Please list deployment operations for details. Please see
https://aka.ms/DeployOperations for usage details.\",\r\n
\"details\": [\r\n ***\r\n \"code\": \"BadRequest
\",\r\n \"message\": \"***\\r\\n \\\"error\\\": ***\\r\\n
\\\"code\\\": \\\"InvalidValuesForRequestParameters\\\",\\r\\n
\\\"message\\\": \\\"Values for request parameters are invalid: kind,
sku. For more information, see - https://aka.ms/storageaccounttypes\\\"
\\r\\n ***\\r\\n***\"\r\n ***\r\n ]\r\n ***\r\n
]\r\n ***\r\n***"***]***
而且我不知道如何分辨其中哪些是Standard_LRS
我在我的環境中嘗試並得到以下結果:
根據MS-DOCS ,位置應該是代碼中的字符串,如美國東部或美國西部。
主要二頭肌:
resource storageAccount 'Microsoft.Storage/storageAccounts@2022-05-01'= {
name: 'venkat9874'
location: 'East US'
sku: {
name: 'Standard_LRS'
}
kind: 'StorageV2'
properties: {
accessTier: 'Hot'
}
}
上面的 Bicep 文件是使用 PowerShell 部署的。
命令:
New-AzResourceGroupDeployment -TemplateFile Main.bicep -ResourceGroupName <your resource grp>
門戶網站:
BlockBlobStorage
種類是Premium SKU的一部分。
為了部署存儲帳戶,您需要稍微修改您的配置,以便SKU name
與所選kind
配置相匹配:
resource storage_account 'Microsoft.Storage/storageAccounts@2022-09-01' = {
name: 'ifmsstorageaccount'
location: location
sku: {
name: 'Premium_LRS'
}
kind: 'BlockBlobStorage'
}
這應該允許您部署存儲帳戶。 顯示的 VM SKU 很奇怪,但我假設您的 bicep 文件中還有一些其他配置是導致該特定錯誤的原因。
希望這可以幫助!
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.