Stefan Pauka on Tue, 18 Apr 2017 09:59:43
I have asked this question on stack overflow about a week ago, but maybe somebody here has another idea. The problem still remains.
I am running inside a Visual Studio Testing Subscription. This subscription has no technical support included. So this is not time-sensitive and I hope there is a way to get this issue solved without switching to another subscription.
I have created a Azure Batch Pool inside a Batch Account. After playing with the scaling formular for a while the pool now says, it is in allocation state "stopping".
This allocation state is the shown state since about three weeks now. Neither resizing using the resize formular (blocked by a "stopping" overlay in the portal) nor deleting the pool works.
After I requested a delete, the pool now has the state "deleting", but stays at allocation state "stopping". Currently the pool has one node running (which it shouldn't according to the formular). This node can still be used for tasks.
So how can I delete the pool? And how can I prevent this issue to occur in our productive environment?
Brian Hoang [MSFT] on Tue, 18 Apr 2017 17:06:05
Can we get your account name, region, pool name, and approximate time of this incident? I'll check our logs to see what's going on.
Stefan Pauka on Mon, 24 Apr 2017 07:54:58
thanks for having a look. I am looking forward to read what you will find out.
I think the transition times should match the time of the incident pretty good.
Region: West Europe
Pool Id: BatchDevPool_MultiTasks
Allocation state: Stopping
Allocation state transition time: March 22, 2017, 09:16:13
State transistion time: March 22, 2017, 13:18:15