Share via

Warning FailedMount 35s (x8 over 103s) kubelet MountVolume.SetUp failed for volume "init-var-volume" : rpc error: code = Unknown desc = mount failed: exit status 32

frank Agyemang 0 Reputation points
2023-10-06T13:28:17.6933333+00:00

Hi suport and team, we are getting an issue after upgrading our Aks cluster from V1.19.11 to V1.25. After the upgrade,Our kubernetes pods would not initialise, they are showing the following error when viewed in Lens ."Warning FailedMount 35s (x8 over 103s) kubelet MountVolume.SetUp failed for volume "init-var-volume" : rpc error: code = Unknown desc = mount failed: exit status 32"

Worth noting we seem to run out of ip addresses during the upgrade so had to shutdown one of the nodepools on the cluster to free up some ip address while we updated the other 2 nodepools.

In the end we seem to have had some of the original ips taken over by other resources.But we managed to configure and resolve that.

not sure if that has an effect on the pods mount issue as well.

any ideas will be appreciated.

Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
1,999 questions
Azure Container Apps
Azure Container Apps
An Azure service that provides a general-purpose, serverless container platform.
346 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. mutaz-msft 2,346 Reputation points Microsoft Employee
    2023-10-09T08:34:23.88+00:00

    Hi @frank Agyemang,

    Exist status 32 means that the AKS node is unable to reach to the Azure file, so can you follow this TSG to verify the connectivity between the AKS node and the Azure files share:

    0 comments