azure - Updating a Virtual Machine Scale Set to add a secret fails with VHD error -
i've deployed virtual machine scale set (vmss) azure part of service fabric cluster. when try redeploy template, enhanced update vmss additional secret, following error. i've verified parameters i'm using correct.
"type": "microsoft.compute/virtualmachinescalesets", // ... "osprofile": { // ... "secrets": [ { "sourcevault": { "id": "[parameters('sourcevaultvalue')]" }, "vaultcertificates": [ { "certificatestore": "[parameters('certificatestorevalue')]", "certificateurl": "[parameters('certificateurlvalue')]" }, { // ******* added ******* "certificatestore": "[parameters('certificatestorevalue')]", "certificateurl": "[parameters('sslcertificateurlvalue')]" } // ******* added ******* ] } ] }, // ...
new-azurermresourcegroupdeployment : 5:46:20 pm - resource microsoft.compute/virtualmachinescalesets 'primary' failed message 'vhd containers being used virtual machine scale set vm instances may not removed. remove vhd container, virtual machine scale set vm instances using must first deleted.' @ d:\myapp\deploy\deploy.ps1:104 char:5 + new-azurermresourcegroupdeployment -resourcegroupname $resourcegr ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + categoryinfo : notspecified: (:) [new-azurermresourcegroupdeployment], exception + fullyqualifiederrorid : microsoft.azure.commands.resources.newazureresourcegroupdeploymentcommand
i've managed work around using powershell instead, based on this answer. still find way have arm template deployment add new certificates or other secrets existing vmss deployment.
update: turns out when had copied down arm template had modified storage account parameters, service fabric configured use prior autogenerated names.
Comments
Post a Comment