Getting CLUSTERS-MGMT-400 error while creating a machinepool in ROSA with a specific instance type

Solution Verified - Updated -

Environment

  • Red Hat OpenShift Service on AWS (ROSA 4)

Issue

  • While attempting to create a new machinepool with a specific instance type, the following error message is observed:
Danger alert:Error adding machine pool
CLUSTERS-MGMT-400: Instance type 'x1e.xlarge' is not supported in availability zone 'us-east-2c'
Operation ID: e5d5ee4c-xxxx-xxxx-xxxx-98fe4039d621
  • Is it possible to only deploy a machine pool to 2/3 AZs?

Resolution

Currently, it is not possible to create a machinepool in 2/3 availability zones nor you can create a ROSA cluster with just 2 AZs . The instance type being selected should have availability in all 3 zones as per your multi AZ cluster.

The best approach would be to switch to a different instance type that is available in all 3 AZs.

Root Cause

The error appears to be related to a particular Availability Zone (us-east-2c in this case) and Red Hat can't do much in it as its related to the cloud provider i.e., AWS. Some Availability Zones don't support particular instance types.

Diagnostic Steps

You can Determine which Availability Zones support your instance type.

To do so, you can follow the below steps from the Amazon EC2 console:

  1. Open the Amazon EC2 console.
  2. Choose the Region where you want to launch the instance.
  3. Select Instance Types.
  4. For Filter instance types, enter your preferred instance type.
  5. Select your preferred instance type.
  6. Under Networking, review the Availability Zones listed under Availability Zones.

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