无法创建新池或调整现有大小:“由于达到调整大小超时,无法分配所需的专用节点数". [英] Unable to create new pools or resize existing: "Desired number of dedicated nodes could not be allocated as the resize timeout was reached."

查看:88
本文介绍了无法创建新池或调整现有大小:“由于达到调整大小超时,无法分配所需的专用节点数".的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试创建一个具有单个节点的新池.我总是得到

I'm trying to create a new pool with a single node. I always get

由于达到调整大小超时,无法分配所需的专用节点数."

"Desired number of dedicated nodes could not be allocated as the resize timeout was reached."

我通过Python API和Azure Portal GUI在服务器虚拟机,配置中进行了尝试,并且还尝试将现有池的大小从1个节点调整为2个,这导致了相同的错误.我什至在第二个订阅上尝试过->同样的错误.我只有 我的订阅上运行了1个VM,这是一个小型A1 linux VM,因此我无法达到核心最大值.我试图得到一条更明确的错误消息,但找不到一条错误消息.

I tried it with serveral VMs, configurations, via Python API and Azure Portal GUI and I also tried to resize a already existing pool from 1 to 2 nodes, which resulted in the same error. I even tried it on a second subscription -> same error. I have only 1 VM running on my subscription, which is a small A1 linux VM, hence I can not have reached the core maximum. I tried to get a more explicity error message, but couldn't find one.

当我在两个不同的订阅上遇到错误时,批处理服务可能存在问题吗?我的服务已在西欧注册.有没有一种调试方法?

As I experience the error on two different subscriptions, might there be a problem with the batch service? My service is registered in Western Europe. Is there a way to debug?

BR

C

推荐答案

今天,我遇到了同样的问题,使用了以前可以完美运行的设置.任何更新或解决方案将不胜感激.

I am having the same problems today using settings that have worked perfectly before. Any updates or solutions would be highly appreciated.

Br

B


这篇关于无法创建新池或调整现有大小:“由于达到调整大小超时,无法分配所需的专用节点数".的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆