Insufficient Resources Error as Diego VM Type Default to m4 from r3 After Upgrading on AWS
search cancel

Insufficient Resources Error as Diego VM Type Default to m4 from r3 After Upgrading on AWS

book

Article ID: 293455

calendar_today

Updated On:

Products

Operations Manager

Issue/Introduction

Symptoms:

Starting Pivotal Cloud Foundry 1.11.0, Operations Manager has updated the VM catalog on AWS. For customers who deployed Diego cells with Operations Manager 1.10, the Diego VMs defaulted to r3 that had 32 GB of RAM. After upgrading Diego, VMs default to m4 that has only 16 GB of RAM and this results in an insufficient memory issue.

 

Environment


Resolution

Select the VM type that has a minimum of 32 GB of RAM manually on the Resource Config Page.

This issue is documented in the Known Issues section for Operations Manager 1.11 Release Notes.