Azure Cloud Service Deployment

Question

I am having a problem deploying my Windows Azure cloud service in an intermediate environment. This is what I often do without problems before I swap Production (as soon as I confirm that everything is fine in Staging). Today, for some reason, I get this error when trying to deploy:

Distribution failed; unable to satisfy request constraints. The requested new service deployment is associated with an Affinity group, or it is intended for a virtual network, or an existing deployment exists under this hosted service. Any of these conditions limit the new deployment to specific Azure resources. Please try again later or try reducing the size of the virtual machine or the number of role instances. Alternatively, if possible, remove the above limitations or try deploying to a different region. Continuous Tracking Id: da5cc14aaba6228683cb4e8888b835e1.

Having seen that my deployment package has not changed since the last successful update of my Staging environment (except for one line of error correction code), I don’t see that this is a problem with my package. I hope this is a temporary issue with the Azure environment - any ideas as to what it might be?

Answer 1

The cluster you are trying to install to has a fragmentation problem. The ops team is engaged and working on the solution, and you can deploy it again tonight or tomorrow.

Additional Information:

• When you create a deployment (either prod or an intermediate slot) in a cloud service, all of your cloud services (both prod and intermediate segments) are tied to a cluster of machines (there are several Mark Russinovich textual videos with more detailed information if you are interested). Therefore, if there is a problem in the cluster or you are trying to expand the size of a virtual machine that is not available in the cluster, such as new D-series machines, you may fail if a particular cluster cannot allocate a request. To solve this problem, you can deploy it to a completely new cloud service that allows the fabric to validate all clusters in this data center / region to satisfy the distribution request.
• Consider a different upgrade strategy for such scenarios. Many services will be updated by creating a new deployment in a new cloud service, obtaining a new URL and IP address, and then changing the CNAME or Record to transfer customers to the new service.
• If you see this problem again, you can get a quick resolution by opening a support incident - http://azure.microsoft.com/en-us/support/options/

Update. We have a new blog post that describes this scenario and common reasons - http://azure.microsoft.com/blog/2015/03/19/allocation-failure-and-remediation/ .

Answer 2

We had a mailing failure problem that recently deployed our cloud service :

Cloud Cloud Service Deployment Error

Distribution failed; unable to satisfy request constraints. The requested new service deployment is associated with an Affinity group, or it is intended for a virtual network, or an existing deployment exists under this hosted service. Any of these conditions limit the new deployment to specific Azure resources. Please try again later or try reducing the size of the virtual machine or the number of role instances. Alternatively, if possible, remove the above limitations or try deploying to a different area.

Distribution Failure - Resolution

• Delete existing cloud service
• Create a new cloud service for different Data Centers or Resource Groups (SSL certificates required)
• Redeploy cloud service package
• Relink VSO Team Projects

I suspect the issue is due to a damaged resource group or recent Azure updates that were not backward compatible with old resource groups.

Answer 3

Could you tell us more about your configuration? In particular, are you deploying a virtual network?

Try expanding to a location, not an affinity group