-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.15.z, 4.17.z, 4.16.z, 4.18
-
None
-
Low
-
None
-
Rejected
-
False
-
Description of problem:
Can't discovery vnet by tag when set up Azure private account when enabled workload identity
Version-Release number of selected component (if applicable):
4.18
How reproducible:
always
Steps to Reproduce:
1.Set up an azure workload identity cluster 2.Set azure private account for image registry oc patch configs.imageregistry/cluster -p {"spec":{"storage":{"azure":{"networkAccess":{"type":"Internal"}}}}} --type=merge 3.
Actual results:
oc get config.image/cluster -o yaml ==== status: conditions: - lastTransitionTime: "2024-10-25T03:37:44Z" message: 'Unable to process private endpoint: failed to discover vnet name, please provide network details manually: "vnet with tags ''map[kubernetes.io_cluster.wxj-1025sts-khxk6:[owned shared] sigs.k8s.io_cluster-api-provider-azure_cluster_wxj-1025sts-khxk6:[owned shared]]'' not found"' reason: AzureError status: Unknown type: StorageExists
Expected results:
The cluster vnet could be find with tag and set up in image registry operator automaticlly.
Additional info:
Must gather log https://drive.google.com/file/d/1Ew1JuxTs9BN2Jx4SCROe9-BY8W7SjD4p/view?usp=sharing