All Pools added to Azure Batch are stuck in resizing

Adam Talbot 1 Reputation point
2020-08-26T18:25:38.797+00:00

Every pool I add to my Azure Batch account becomes stuck in "resizing". This happens whether I use an autoscale formula or fixed size. It doesn't seem to matter what image or VM size I select.

The error is as follows:

Code: AllocationTimedout

Message:
Desired number of dedicated nodes could not be allocated as the resize timeout was reached

Values:
n/a

Azure Batch
Azure Batch
An Azure service that provides cloud-scale job scheduling and compute management.
314 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. KarishmaTiwari-MSFT 18,652 Reputation points Microsoft Employee
    2020-08-27T02:42:42.963+00:00

    @Adam Talbot Are you creating a pool using the Shared Image Gallery or a managed image resource?

    In the past we have seen this error occurring if one of these criteria is not met:

    1. Currently, Batch only supports generalized Shared Images. You can't create a custom image pool from a specialized Shared Image at this time.
      https://learn.microsoft.com/en-us/azure/batch/batch-sig-images#prepare-a-shared-image
    2. The managed image resource should exist for the lifetime of the pool to allow scale-up and can be removed after the pool is deleted.
      https://learn.microsoft.com/en-us/azure/batch/batch-custom-images#prerequisites

    Please check and let me know if any of this applies to you.

    Converting this comment to answer for anyone to troubleshoot using these steps if they see similar issue.

    0 comments No comments

  2. Adam Talbot 1 Reputation point
    2020-08-27T08:31:30.547+00:00

    I am using the ubuntu-server-container offer, from microsoft-azure-batch, using SKU 16.04-lts. There is no custom image and I am using Docker to add any software dependencies.

    The problem has fixed itself this morning. I made no adjustments to the code, environment variables or deployments.