Not able to add machine pools on Hypershift cluster

Solution Verified - Updated -

Environment

  • Red Hat OpenShift Service on AWS (ROSA) with hosted control planes (Hypershift)

Issue

When attempting to create a new machine pool we are getting error:

"Failed to create or update node pool on cluster:<cluster-name>","cr_type":"CloudRockCluster","cr_name":"<cluster-name>","id":"<cluster-id>","error":"status is 500, identifier is '500', code is 'CLUSTERS-MGMT-500' and operation identifier is 'xxx-xxx-xxx-xxx-xxxx'"}

Resolution

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.

Note: You may see this issue if your Hypershift cluster is created before May 3, 2023

  • Open a support ticket with the Red Hat OpenShift Support Team and report the issue.
  • Our SRE team need to apply a workaround to fix this issue

Root Cause

OpenShift Cluster Manager recently rolled out create ingress configmap to control ingress endpoint publish strategy changes.
Customers who have Hypershift clusters created before the changes made will see issues with creating new machine pool, as the new change is expecting a config map that was not created with the old hypershift clusters.

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