[azure-disk-csi-driver] ARO HCP uses UserAssignedIdentityCredentials could not provision volume    

4.19.0-0.nightly-2025-02-26-050226    

  Always 

    1. Install ARO hypershift cluster uses UserAssignedIdentityCredentials mode.
    2. Create pvc using the managed-csi(azure disk csi provisioner) storageclass, and create pod consume the pvc.
    3. Check the pvc could provision successfully and pod could start running.
    

  In step3: the pvc provision failed of ->
I0225 13:44:52.851851       1 controllerserver.go:281] begin to create azure disk(pvc-99f969ab-3629-4729-87c7-e796e081f27e) account type(Premium_LRS) rg(generic-managed-rg) location(eastus) size(5) diskZone() maxShares(0)
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x68 pc=0x21ced59]

goroutine 516 [running]:
sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.(*ManagedDiskController).CreateManagedDisk(0xc000624668, {0x2e5c030, 0xc0004fef30}, 0xc00030d040)
	/go/src/github.com/openshift/azure-disk-csi-driver/pkg/azuredisk/azure_managedDiskController.go:271 +0x1759
sigs.k8s.io/azuredisk-csi-driver/pkg/azuredisk.(*Driver).CreateVolume(0xc00033c800, {0x2e5c030, 0xc0004fef30}, 0xc00029ec80)
	/go/src/github.com/openshift/azure-disk-csi-driver/pkg/azuredisk/controllerserver.go:332 +0x36c5
...  

 In step3: the pvc could provision successfully and pod could start running.   

 From the csi driver controller logs we could see ->
azure_auth.go:175] "No valid auth method found" logger="GetServicePrincipalToken"

It seems current cloud-provider-azure(https://github.com/openshift/azure-disk-csi-driver/blob/master/go.mod#L46) depeddency does not contains the support for UserAssignedIdentityCredentials.