When creating an OpenShift cluster on the Azure platform via Hive, it is possible to override the Azure resource group in which the cluster is created within the install config.

Hive MachinePools are unaware of this resource group override and perform operations such as checking for an image gallery in the resource group against the default resource group name which is based on the ClusterID.

This results in errors such as the following where "ocp-lab-68x4h-rg" is used instead of the custom resourceGroupName defined in the install config.

"Message=\"The client 'xx' with object id 'xx' does not have authorization to perform action 'Microsoft.Compute/images/read' over scope '/subscriptions/xx/resourceGroups/ocp-lab-68x4h-rg/providers/Microsoft.Compute'"

4.14.0

Reproducible with a user provided resource group.

1. Create an Azure cluster using Hive with a custom resource group set within the install config.
2. Create an additional MachinePool for the cluster or to manage the existing worker MachineSets.
3. Observe authorization error which is looking in the default resource group name which is based on the clusterID.

MachineSet generation fails.

MachineSet generation succeeds.