ROSA HCP cluster machine pool stuck in pending state because of KMS setting

Solution Verified - Updated

Environment

  • Red Hat OpenShift Service on AWS (ROSA) HCP
    • 4

Issue

  • ROSA HCP cluster machine pool is stuck in a pending state because of the KMS setting

Resolution

  • Follow the below document to check if the policy and setting are correct can help to solve this issue

creating-cluster-with-aws-kms-key

Root Cause

  • Check the EC2 page on AWS, found there are below errors exist
Client.InvalidKMSKey.InvalidState: The KMS key provided is in an incorrect state
SBR
Product(s)
Components
Category
Tags

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.