Cluster installation failed with error code OCM3013: AWSVPCLimitExceeded

Solution Verified - Updated -

Environment

  • Red Hat Openshift Container Platform (OCP 4)
  • Red Hat OpenShift Service on AWS (ROSA 4)
  • Red Hat Openshift Dedicated 4 (OSD 4)

Issue

Disclaimer: Links contained herein to external website(s) are provided for convenience only. Red Hat has not reviewed the links and is not responsible for the content or its availability. The inclusion of any link to an external website does not imply endorsement by Red Hat of the website or their entities, products or services. You agree that Red Hat is not responsible or liable for any loss or expenses that may result due to your use of (or reliance on) the external site or content.

  • Cluster installation failed with error code OCM3013: AWSVPCLimitExceeded.
  • Following error log is observed in the install logs:
OCM3013 Cluster installation failed. VPC limit exceeded. Clean unused VPCs or increase quota and try again.

Resolution

The reason behind this error is that you've reached the quota for the number of VPCs. You can clean unused VPCs to reclaim quota or request a quota increase from AWS and try again.

Option A : Request a quota increase (Recommended)

You can request a quota increase using Service Quotas and AWS Support Center. Increases are not granted immediately. It might take a couple of days for your increase to become effective.

How to request a quota increase?

To request a service quota increase:

  1. Sign in to the AWS Management Console and open the Service Quotas console at here

  2. In the navigation pane, choose AWS services.

  3. Choose an AWS service from the list, or type the name of the service in the search box.

  4. If the quota is adjustable, you can choose the button or the name, and then choose Request quota increase.

  5. For Change quota value, enter the new value. The new value must be greater than the current value.

  6. Choose Request.

To view any pending or recently resolved requests, choose Dashboard from the navigation pane. For pending requests, choose the status of the request to open the request receipt. The initial status of a request is Pending. After the status changes to Quota requested, you'll see the case number with AWS Support. Choose the case number to open the ticket for your request.

After the request is resolved, the Applied quota value for the quota is set to the new value.

Option B: Clean unused VPC

Requirement:

Before you can delete a VPC, you must first terminate or delete any resources that created a requester-managed network interface in the VPC. For example, you must terminate your EC2 instances and delete your load balancers, NAT gateways, transit gateways, and interface VPC endpoints.

To delete your VPC using the console:

  1. Open the Amazon EC2 console by clicking here.

  2. Terminate all instances in the VPC. For more information, see Terminate Your Instance in the Amazon EC2 User Guide for Linux Instances.

  3. Open the Amazon VPC console by clicking here.

  4. In the navigation pane, choose Your VPCs.

  5. Select the VPC to delete and choose Actions, Delete VPC.

  6. If you have a Site-to-Site VPN connection, select the option to delete it; otherwise, leave it unselected. Choose Delete VPC.

For more information, please refer the official AWS documentation.

Root Cause

AWS account has default quotas, formerly referred to as limits, for each AWS service. If the quota for a service exceeds its limit, the customer has to request a quota increase from AWS (Recommended) or they can choose to delete unused objects and reclaim quota.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments