Pivotal Knowledge Base

Follow

`ResizeDiskError` error on Azure Pivotal Cloud Foundry installation when installing Pivotal Cloud Foundry Runtime for Windows

Environment

IaaS: Azure

Pivotal Cloud Foundry® (PCF): 1.10.x

PCF Runtime for Windows: 1.10.x

Symptom

On your PCF 1.10.x environment installed on Azure, you have already deployed Ops Manager and installed Elastic Runtime. Afterward, you are attempting to install the PCF Runtime for Windows, which is failing. You might receive the following error:

Error message: {
  "startTime": "2017-05-25T10:38:25.2211353+00:00",
  "endTime": "2017-05-25T10:38:25.533667+00:00",
  "status": "Failed",
  "error": {
    "code": "ResizeDiskError",
    "message": "Disk size reduction is not supported. Current size is 136367309312 bytes, requested size is 71940702720 bytes."
  }

This error occurs because the minimum VHD size of disk images on Azure is 127GB. While we’re producing the Stemcell in the pipeline (hosted on Azure!), we effectively “snapshot” the disk once we’ve installed the Bosh agent, related dependencies, and set the local policies. When we create the image snapshot, it’s 127GB.

Thus, when you deploy VMs via `BOSH` and the light Stemcell we provide, the required disk size is 127GB or bigger.

Resolution

To get past this issue, you will need to make the following changes in Ops Manager:

Change 1

In your Ops Manager Dashboard, open the PCF Runtime for Windows Tile -> Settings Tab -> Resource Config Section -> and set the VM TYPE as Standard_DS12_v2 (cpu: 4, ram: 28GB, disk: 200GB) for the Windows Diego Cells. See below:

screenshot_1.png

After doing this, click the save button, make sure the right VM TYPE is selected for the Windows Diego Cells, than proceed to Change 2.

Change 2

In your Ops Manager Dashboard, open the Ops Manager Director Tile -> Settings Tab -> Resource Config Section -> and set the VM TYPE as Standard_DS3_v2 (cpu: 4, ram: 14GB, disk: 200GB) for the Master Compilation Job. See below:

screenshot_2.png

After doing this, click the save button, make sure the right VM TYPE is selected for the Master Compilation Job, then proceed back to Ops Manager home page, and Apply Changes again. This time you should be able to successfully get past the ResizeDiskError

Additional Information

We have provided Microsoft our Feedback regarding this constraint.

Comments

Powered by Zendesk