none
Compute.ConstrainedAllocationFailed

    Question

  • Hello,

    I have been trying to upload a web role and worker role to an empty staging slot all day and keep seeing the error below.  I have plenty of cores available and have tried uploading both through visual studio and manually with the same result.  I recently upgraded this project to the 2.2 sdk and wondering if this is related.  I have been able to upload another project that is on the previous SDK.  This project, however, was working fine after the upgrade to 2.2.    My last successful upload was two days ago.   The dashboard shows no issues in my region which is WEST US.   Any help would be much appreciated.

    Allocation failed; unable to satisfy constraints in request. The requested new service deployment is bound to an Affinity Group, or it targets a Virtual Network, or there is an existing deployment under this hosted service. Any of these conditions constrains the new deployment to specific Azure resources. Please retry later or try reducing the VM size or number of role instances. Alternatively, if possible, remove the aforementioned constraints or try deploying to a different region.

    Thanks,

    Chaos

    Thursday, November 07, 2013 12:07 AM

Answers

  • I am having this issue too. I am in WEST US. This is really nuts and is very frustrating.

    The error message is horrible and less than helpful. I am getting ready to bail and move the whole project to Amazon since I am trying to roll out a hotfix. 

    Notice there have been issues with it, but they publish it as being fixed. It is not fixed yet, but this assures me that no one is working on it currently.


    Casey



    Thursday, November 07, 2013 12:33 AM

All replies

  • I am having this issue too. I am in WEST US. This is really nuts and is very frustrating.

    The error message is horrible and less than helpful. I am getting ready to bail and move the whole project to Amazon since I am trying to roll out a hotfix. 

    Notice there have been issues with it, but they publish it as being fixed. It is not fixed yet, but this assures me that no one is working on it currently.


    Casey



    Thursday, November 07, 2013 12:33 AM
  • This finally seems to be working with no changes on my part to the deployment.

    Casey

    Thursday, November 07, 2013 1:46 AM
  • Mine is working too.  Thanks for replying... I was going crazy.
    Thursday, November 07, 2013 2:38 AM