AKS PVC is not attached to Pod

Question

AKS PVC is not attached to Pod

V. Sai Krishna 0

Hi folks.

I have AKS cluster. I have deployed a deployment and it triggered ndoe scaling up. Then a pod of this deployment has been scheduled on the new node. The PVC and PV created, and all are in Bound status. But it is not attached to the pod. Even though we have contributor role.

Here is the pod describe result.

Unable to attach or mount volumes: unmounted volumes=[storage], unattached volumes=[storage kube-api-access-pmmwd sc-datasources-volume config ldap]: timed out waiting for the condition

AttachVolume.Attach failed for volume "pvc-4e251a29-fa03-4d86-be36" : rpc error: code = Internal desc = Attach volume /subscriptions//resourceGroups/h_southcentralus/providers/Microsoft.Compute/disks/pvc-4e251a29-fa03-4d86-be36 to instance aks-rancher-0-1 failed with could not find disk(/subscriptions/7/resourcegroups/h_southcentralus/providers/microsoft.compute/disks/pvc-4e251a29-fa03-4d86-be36 in current disk list(len: 5) nor in diskMap(map[])

kobulloc-MSFT 26,811 Reputation points Microsoft Employee Moderator

2024-03-18T18:29:12.2+00:00

Hello, @V. Sai Krishna !

If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

1 answer

Your answer

kobulloc-MSFT 26,811 Reputation points Microsoft Employee Moderator

2024-03-18T18:29:12.2+00:00

Hello, @V. Sai Krishna !

If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

Answer 1

Deepanshu katara 16,790 MVP Moderator

Hi,

This could happen due to below reasons

Disk Provisioning: The disk might not have been provisioned properly in Azure. Verify in the Azure portal whether the disk associated with the Persistent Volume Claim (PVC) exists and is in the same subscription and resource group.
Node Disk Mounts: Ensure that the node (aks-rancher-0-1) is correctly configured to mount disks. Sometimes, node configuration issues can prevent it from accessing disks.
Node Permission Issues: Check if the node has the necessary permissions to access disks. Ensure that the service principal used by the node has the required permissions to attach disks to the virtual machine.

Please check below doc --> https://learn.microsoft.com/en-us/azure/aks/azure-csi-disk-storage-provision

V. Sai Krishna 0 Reputation points

2024-03-06T11:18:08.2966667+00:00

Hello @Deepanshu katara ,

Basically, the existing deployments and volumes are working fine. We are facing this issue recently is there any particular reason behind this?
Deepanshu katara 16,790 Reputation points MVP Moderator

2024-03-06T13:49:14.6+00:00

Hi ,

Have you seen that the access modes supported?

Access Modes

Note that, Except for ReadWriteOncePod, other mode allows multiple pods to access the volume on the same node.
V. Sai Krishna 0 Reputation points

2024-03-08T02:47:27.6+00:00

yes we have enough permission for the storage account and have enough access modes permission also. what else might required @Deepanshu katara

Share via

AKS PVC is not attached to Pod

1 answer

Your answer