Troubleshooting for Azure Red Hat OpenShift

This article details some common issues encountered while creating or managing Microsoft Azure Red Hat OpenShift clusters.

Retrying the creation of a failed cluster

If creating an Azure Red Hat OpenShift cluster using the az CLI command fails, retrying the create will continue to fail. Use az openshift delete to delete the failed cluster, then create an entirely new cluster.

Hidden Azure Red Hat OpenShift cluster resource group

Currently, the Microsoft.ContainerService/openShiftManagedClusters resource that's automatically created by the Azure CLI (az openshift create command) is hidden in the Azure portal. In the Resource group view, check Show hidden types to view the resource group.

Screenshot of the hidden type checkbox in the portal

Creating a cluster results in error that no registered resource provider found

If creating a cluster results in an error that No registered resource provider found for location '<location>' and API version '2019-04-30' for type 'openShiftManagedClusters'. The supported api-versions are '2018-09-30-preview, then you were part of the preview and now need to purchase Azure virtual machine reserved instances to use the generally available product. A reservation reduces your spend by pre-paying for fully managed Azure services. Refer to What are Azure Reservations to learn more about reservations and how they save you money.

Next steps