Log from pv_controller.go regarding volume provisioning problem on 1.9.7

[DonMartin76]

This is what I see in the controller manager logs, lots of these, where the azure storage controller tries to access a storage account in the wrong resource group:

I0425 13:47:20.952988       1 event.go:218] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"wekamedia", Name:"postgres-wekamedia-aurora-postgres", UID:"b4b1fc09-488e-11e8-8c3b-000d3ab7f8fa", APIVersion:"v1", ResourceVersion:"7511", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' Failed to provision volume with StorageClass "default": azureDisk - account ds6c822a4d484211eXXXXXX does not exist while trying to create/ensure default container
I0425 13:47:35.951122       1 pv_controller.go:1379] failed to provision volume for claim "somenamespace/aurora-postgres" with StorageClass "default": azureDisk - account ds6c822a4d484211eXXXXXX does not exist while trying to create/ensure default container

Feel free to just close this if I got you wrong. It does seem you know these issues very well. That using managed disks fixes this I was not aware of. I was even not aware you could switch those on.

References:

• Multiple clusters - dynamic PVCs try to access wrong storage account (of other resource group) Azure/acs-engine#2768
• Azure disk fails to attach and mount, causing rescheduled pod to stall following node disruption  kubernetes/kubernetes#46421

[andyzhangx]

@DonMartin76 thanks for reporting, I have already identified this issue. Pls use ManagedDisks instead, thanks.