VM Disk Size Discrepancy when Deploying via Content Library

Products

• VMware Tanzu Platform - Cloud Foundry

Issue/Introduction

When deploying an Ops Manager 3.2.3 OVA from a vSphere Content Library, the resulting Virtual Machine (VM) displays a primary hard disk size of 50 GB. This differs from the expected default size of 160 GB typically seen during a direct OVA deployment.

Environment

• Hypervisor: VMware ESXi 5.1 and later (VM Version 9)

• Management: vSphere Client / vCenter Server

• Deployment Method: OVF/OVA template deployed via Content Library

• Product: Ops Manager 3.2.3

Cause

This behavior is not a bug but a known limitation regarding how Content Library handles disk resizing during the deployment process.

When an OVA is deployed directly, the OVF descriptor can trigger a resize of the disks to the capacity defined in the metadata. However, when deploying via the Content Library, the system defaults to the physical disk size defined strictly within the .vmdk files themselves. In this specific case, the base image size is 50 GB, and the instruction to expand to 160 GB is bypassed by the Content Library deployment workflow.

 

Resolution

To ensure the VM is deployed with the correct 160 GB disk size, choose one of the following methods:

1. Direct Deployment: Deploy the OVA directly from your local machine or a URL using the "Deploy OVF Template" wizard instead of using the Content Library.

2. Manual Resize: If the VM has already been deployed (and is currently Powered Off), you can manually increase the disk size in the VM hardware settings.

Additional Information

See KB Article ID: 329823