[英]Azure Cloud Service Deployment
I am having an issue deploying to the Staging environment of my Windows Azure Cloud Service. 我在部署到Windows Azure云服务的登台环境时遇到问题。 This is something I do frequently without issue before doing a swap to Production (once I have validated everything is OK in Staging).
这是我在交换到生产之前经常没有问题的事情(一旦我验证了一切都可以在分段中完成)。 Today for some reason I am getting this error when trying to deploy:
今天由于某种原因我在尝试部署时遇到此错误:
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.
请求的新服务部署绑定到Affinity Group,或者它定位到虚拟网络,或者此托管服务下存在现有部署。 Any of these conditions constrains the new deployment to specific Azure resources.
这些条件中的任何一个都会将新部署限制为特定的Azure资源。 Please retry later or try reducing the VM size or number of role instances.
请稍后重试或尝试减小VM大小或角色实例数。 Alternatively, if possible, remove the aforementioned constraints or try deploying to a different region.
或者,如果可能,删除上述约束或尝试部署到不同的区域。 The long running operation tracking ID was: da5cc14aaba6228683cb4e8888b835e1.
长时间运行的操作跟踪ID为:da5cc14aaba6228683cb4e8888b835e1。
Seeing as my deployment package has not changed since the last time I successfully performed an update of my Staging environment (apart from one line of code for a bug fix) I can't see this being an issue with my package. 自从我上次成功执行Staging环境更新(除了一行代码修复错误)以来,我的部署包没有改变,我看不出这是我的包的问题。 I am hoping this is transient Azure environment issue - anyone any ideas as to what this may be?
我希望这是暂时的Azure环境问题 - 任何人都有任何想法,这可能是什么?
There is a fragmentation issue in the cluster you are trying to deploy to. 您尝试部署到的群集中存在碎片问题。 The ops team is engaged and working to resolve and you should be able to deploy again later tonight or tomorrow.
操作团队参与并努力解决,您应该能够在今晚或明天再次部署。
Some additional information: 一些其他信息:
Update: We have a new blog post that describes this scenario and the common causes - http://azure.microsoft.com/blog/2015/03/19/allocation-failure-and-remediation/ . 更新:我们有一篇新的博客文章描述了这种情况和常见原因 - http://azure.microsoft.com/blog/2015/03/19/allocation-failure-and-remediation/ 。
We had a similar allocation failed issue recently deploying our Azure Cloud Service : 最近部署我们的Azure云服务时,我们遇到了类似的分配失败问题:
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.
请求的新服务部署绑定到Affinity Group,或者它定位到虚拟网络,或者此托管服务下存在现有部署。 Any of these conditions constrains the new deployment to specific Azure resources.
这些条件中的任何一个都会将新部署限制为特定的Azure资源。 Please retry later or try reducing the VM size or number of role instances.
请稍后重试或尝试减小VM大小或角色实例数。 Alternatively, if possible, remove the aforementioned constraints or try deploying to a different region.
或者,如果可能,删除上述约束或尝试部署到不同的区域。
I suspect the issue has something to do with a corrupt resource group or recent Azure upgrades that were not backwards compatible with older resource groups. 我怀疑该问题与损坏的资源组或最近的Azure升级有关,这些升级与旧资源组无向后兼容。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.