Azure / Azure/BatchExplorer

Error about scaling failing when actually worked

Open
#2,085 1 comment 0 reactions 0 assignees View on GitHub
:bug: bug
Dominant language
TypeScript
Stars
205
Forks
75
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
Red bar with "Desired number of dedicated nodes could not be allocated as the resize timeout was reached"

![image](https://user-images.githubusercontent.com/50909/65040819-2ea84680-d94d-11e9-8168-a472bb5e0372.png)

**To Reproduce**
Steps to reproduce the behavior:
1. Have auto-scaling pool
2. Auto-scaling rule sets pool size to 0
3. Pool scales to 0
4. Batch Explorer shows above error, red numbers as shown in screenshot
5. Click "Fix", issue persists

This shouldn't be a warning as the pool has successfully scaled down to 0

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.