Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
All solutions
    • All solutions for Managed Service for Kubernetes
    • Fixing the "timed out waiting for the condition" error when mounting a PVC
    • Resolving the "timed out waiting for the condition" error when mounting a volume with a large number of files
    • Hosts of the Managed Service for Kubernetes node groups stay in the Reconciling status for a long time
    • Constant restarts of the kube-dns-autoscaler pod
    • Number of nodes in the group fails to decrease
    • Resolving the "Multi-Attach error for volume" error
    • Resolving the "DEADLINE_EXCEEDED" error
    • Adding and updating Linux SSH keys on Managed Services for Kubernetes node group hosts
    • Assigning static external IP addresses for Managed Service for Kubernetes cluster nodes
    • Granting internet access to Kubernetes nodes
    • How to change the network or subnet for an MDB cluster
    • How to create an internal Ingress controller

In this article:

  • Issue description
  • Solution
  1. Managed Kubernetes
  2. Fixing the "timed out waiting for the condition" error when mounting a PVC

Fixing the «timed out waiting for the condition» error when mounting a PVC

Written by
Yandex Cloud
Updated at September 12, 2023
  • Issue description
  • Solution

Issue descriptionIssue description

When mounting a Persistent Volume Claim (PVC) to the Managed Service for Kubernetes cluster, you see the following error in your Kubelet output and service logs:

Unable to attach or mount volumes: unmounted volumes=[<PVC_NAME>],
unattached volumes=[conf kube-api-access-r9rql data]: timed out waiting for the condition

SolutionSolution

Restart the VM running the cluster's worker node hosting the pod with the problem storage.
Be sure to run a cold restart, shutting down the VM. This restarts the QEMU process on the hypervisor with a new ID.

For a cold VM restart, use the Stop button, wait for the Stopped status, then start the VM from the Compute Cloud management console or YC CLI.

Was the article helpful?

Previous
All solutions for Managed Service for Kubernetes
Next
Resolving the "timed out waiting for the condition" error when mounting a volume with a large number of files
Yandex project
© 2025 Yandex.Cloud LLC