-
Bug
-
Resolution: Done
-
Minor
-
None
-
4.14, 4.15, 4.16, 4.17, 4.18, 4.19
-
Quality / Stability / Reliability
-
False
-
-
1
-
None
-
None
-
None
-
None
-
None
-
OSDOCS Sprint 273
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Slack Thread: https://redhat-internal.slack.com/archives/C04TMSTHUHK/p1738897393275439?thread_ts=1738750794.938799&cid=C04TMSTHUHK In reproduce of OCPBUGS-49413, it performed the procedure of enabling Microsoft Entra Workload ID but failed. The root cause was the cluster installed with the specified VNET in another RG so it should be inputted with parameter --network-resource-group-name when running ccoctl azure create-managed-identities
Version-Release number of selected component (if applicable):
4.14+
How reproducible:
Always
Steps to Reproduce:
- Install a cluster with the existing VNET in install-config
- Run ccoctl azure create-all/create-managed-identities as in the documents
Actual results:
The cluster install or the procedure of enable Microsoft Entra Workload ID failed
Expected results:
The cluster install or the procedure of enable Microsoft Entra Workload ID is successful
Additional info:
There are 2 document places to be updated: (1) https://docs.openshift.com/container-platform/4.18/installing/installing_azure/ipi/installing-azure-customizations.html#cco-ccoctl-creating-at-once_installing-azure-customizations (2)https://docs.openshift.com/container-platform/4.18/post_installation_configuration/changing-cloud-credentials-configuration.html#enabling-entra-workload-id-existing-cluster_changing-cloud-credentials-configuration