ROSA 4.12 cluster creation failure

Solution Unverified - Updated -


  • Red Hat OpenShift Service on AWS (ROSA)
    • 4.12.0 through 4.12.2
  • rosa CLI
    • 1.2.11+


  • ROSA 4.12 Cluster creation takes a long time and/or fails.
  • Need to specify/upgrade ROSA account roles and policies for a specific minor version of ROSA.
  • The rosa create cluster command outputs an error about missing account roles:

    No account roles found. You will need to manually set them in the next steps or run 'rosa create account-roles' to create them first.


The issue described applies to new clusters where the attempted install version is 4.12.0 through 4.12.2. The issue is fixed with ROSA 4.12.3 and onwards.

Note: Before starting the installation of ROSA 4.12, make sure that the rosa CLI version used is the latest one (1.2.11 at the time of writing) from the rosa mirror.

Issue 1: Cluster installation does not start because of missing account roles.

Running the rosa create cluster --version 4.12.7 is prompting for account roles to be created even though the rosa create account-roles command was previously run.

The change to the default installed version now requires 4.12 account roles to be explicitly created. Use the command below to create them.

$ rosa create account-roles --version 4.12

Once created, retry the rosa create cluster --version 4.12.7 command.

Issue 2: ROSA 4.12 cluster installation fails

Red Hat noticed increased cluster creation failure rates and decided to set OpenShift 4.11 as the default ROSA version. However, OpenShift 4.12 is still available by using the --version parameter as shown in the following examples:

  • To create a ROSA 4.11 cluster:

    $ rosa create account-roles
    $ rosa create cluster [...]
  • To create a ROSA 4.12 cluster:

    $ rosa create account-roles --version 4.12
    $ rosa create cluster --version 4.12.7 [...]

Note: The account-roles and policies are backwards-compatible, so having the latest version will allow users to create clusters of that version or older.

Root Cause

Occasionally, Red Hat may deem it necessary to alter the default version of newly created clusters as a precaution.

Diagnostic Steps

Use the following command to list available ROSA versions.

$ rosa list versions
4.11.22    yes        
4.12.0     no  

The output above indicates ROSA 4.12 is not the default, but is available. Creating resources without specifying the version will default to ROSA 4.11.

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.