rook: Unable to mount volume

Is this a bug report or feature request?

  • Bug Report

Bug Report

What happened: I have deployed rook-operator with helm chart and very basic cluster and block-storage pool from doc. When i created PVC, PV was created, but can not be mounted to a pod. I have this:

Unable to mount volumes for pod ***": timeout expired waiting for volumes to attach/mount for pod "***". list of unattached/unmounted volumes=[data]

I can see that volume was successfully created in operator logs

What you expected to happen: Volume mounted to a pod

How to reproduce it (minimal and precise): Deploy rook-alpha/rook with helm Create Cluster as described in quickstart Create Blockstorage Pool as described in quickstart Create SC for this Pool Create PVC

Environment:

  • OS ubuntu 15.04
  • Kernel (e.g. uname -a): Linux dev1-master-0 4.13.0-1018-azure #21-Ubuntu SMP Thu May 17 13:58:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  • Cloud provider or hardware configuration: AzureRM
  • Rook version (use rook version inside of a Rook Pod): v0.7.1
  • Kubernetes version (use kubectl version): 0.9.5
  • Kubernetes cluster type (e.g. Tectonic, GKE, OpenShift): Kubespray on Azure
  • Ceph status (use ceph health in the Rook toolbox): HEALTH_OK

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 17 (10 by maintainers)

Most upvoted comments

Future travelers:

I had all these symptoms but in my case it was resolved by restarting the kubelet. K8s 1.11 Fedora 28

I followed an old guide for k8s 1.7 https://github.com/rook/rook/blob/master/Documentation/common-issues.md#kubelet-restart