microsoft / MLOpsPython

MLOps using Azure ML Services and Azure DevOps
MIT License
1.2k stars 1.1k forks source link

Error during resource provisioning stage: Account update is not supported yet #364

Closed camer314 closed 3 years ago

camer314 commented 3 years ago

I am working through the tutorial and am on the first step where we deploy the resources to the resource group however this is failing with a weird storage account error as below. Any ideas?

2021-05-20T02:22:58.9759080Z ##[section]Starting: Deploy MLOps resources to Azure 2021-05-20T02:22:58.9771002Z ============================================================================== 2021-05-20T02:22:58.9771668Z Task : Azure resource group deployment 2021-05-20T02:22:58.9772193Z Description : Deploy an Azure Resource Manager (ARM) template to a resource group and manage virtual machines 2021-05-20T02:22:58.9772668Z Version : 2.184.1 2021-05-20T02:22:58.9773023Z Author : Microsoft Corporation 2021-05-20T02:22:58.9773487Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/deploy/azure-resource-group-deployment 2021-05-20T02:22:58.9774083Z ============================================================================== 2021-05-20T02:22:59.8670286Z ##[warning]Resource file has already set to: /home/vsts/work/_tasks/AzureResourceGroupDeployment_94a74903-f93f-4075-884f-dc11f34058b4/2.184.1/node_modules/azure-pipelines-tasks-azure-arm-rest-v2/module.json 2021-05-20T02:22:59.9396386Z Checking if the following resource group exists: IXS-NGIT-WESTEUROPE-SYNAPSE. 2021-05-20T02:22:59.9475975Z (node:2110) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. 2021-05-20T02:22:59.9479726Z Resource group exists: true. 2021-05-20T02:22:59.9486710Z Creating deployment parameters. 2021-05-20T02:22:59.9510453Z The detected encoding for file '/home/vsts/work/1/s/environment_setup/arm-templates/cloud-environment.json' is 'utf-8' 2021-05-20T02:23:00.3213906Z Starting template validation. 2021-05-20T02:23:00.3562327Z Deployment name is cloud-environment-20210520-022300-1a45 2021-05-20T02:23:01.7745576Z Template deployment validation was completed successfully. 2021-05-20T02:23:01.7748682Z Starting Deployment. 2021-05-20T02:23:01.7751284Z Deployment name is cloud-environment-20210520-022300-1a45 2021-05-20T02:23:48.3515968Z There were errors in your deployment. Error code: DeploymentFailed. 2021-05-20T02:23:48.3521988Z ##[error]At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details. 2021-05-20T02:23:48.3527603Z ##[error]Details: 2021-05-20T02:23:48.3568012Z ##[error]BadRequest: Storage Account update is not supported yet 2021-05-20T02:23:48.3572488Z ##[error]Check out the troubleshooting guide to see if your issue is addressed: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-resource-group-deployment?view=azure-devops#troubleshooting 2021-05-20T02:23:48.3577054Z ##[error]Task failed while creating or updating the template deployment. 2021-05-20T02:23:48.3635489Z ##[section]Finishing: Deploy MLOps resources to Azure

sen0204 commented 3 years ago

Facing same issue, please help

j-so commented 3 years ago

Are you using an existing AzureML workspace? If so, you can skip this step. Just make sure that you are setting your variables correctly (WORKSPACE_NAME, RESOURCE_GROUP, LOCATION, etc).

The environment setup pipeline will attempt to create a new storage account and workspace, and then try to link the two together. If the workspace already exists and uses a different storage account, you'll get this error. If you already have a workspace, there's no need to run this pipeline.

camer314 commented 3 years ago

@j-so you are correct, I went back and tried with a new workspace and it completed successfully