Problems with Azure VMs of different sizes

Just a quick note…

If you’re building an Azure Cloud Service with multiple Virtual Machines of varying sizes, does it matter which order you create Azure VMs?

I created a new Azure Cloud Service by building a machine of size Basic_A3. Next on the build list was a machine of size A5. Except that the New-AzureVM command failed:

New-AzureVM : Compute.CannotUpgradeDeploymentToNewRoleSize : Unable to upgrade the deployment. The requested VM size 'A5' may not be
available in the resources supporting the existing deployment. Please try again later, try with a different VM size or smaller number
of role instances, or create a deployment under an empty hosted service with a new affinity group or no affinity group binding.
At P:\My Documents\WindowsPowerShell\BuildVMs.ps1:359 char:6
+     |New-AzureVM -ServiceName $myServiceName -Location $myLocation -WaitForBoot  ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [New-AzureVM], ComputeCloudException
    + FullyQualifiedErrorId : Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.PersistentVMs.NewAzureVMCommand

On Azure’s portal, hunt for the errors in the deployment logs, and find an XML file, the useful part of which is:

    <OperationStatus>
        <ID>15719df4-e93e-1521-9af3-adddb6efe222</ID>
        <Statu>Failed</Status>
        <HttpStatusCode>403</HttpStatusCode>
        <Error>
            <Code>Compute.CannotUpgradeDeploymentToNewRoleSize</Code>
            <Message>Unable to upgrade the deployment. The requested VM size 'A5' may not be available in the resources supporting the existing deployment. Please try again later, try with a different VM size or smaller number of role instances, or create a deployment under an empty hosted service with a new affinity group or no affinity group binding.</Message>
        </Error>
    </OperationStatus>

On the off-chance it was a problem with starting off with a machine in the Basic range (sounds like a discount supermarket label), I tried again, creating the service with an A5, adding the Basic_A3 I needed, and then, for fun, adding a Standard_D12. Except that failed with the same problem.

So, to answer my question at the top… Yes. Yes it does matter. Build the biggest one you need first.

Advertisements
This entry was posted in SQLServerPedia Syndication and tagged , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s