rook: PVC Provisioning Fails with "no available topology found" for StorageClass "rook-cephfs"

Is this a bug report or feature request?

  • Bug Report

Deviation from expected behavior: When creating a PVC using the rook-cephfs StorageClass, the PVC remains in Pending state with the error:
failed to provision volume with StorageClass "rook-cephfs": error generating accessibility requirements: no available topology found

Expected behavior: PVC should be successfully provisioned and transition to Bound state when using a valid StorageClass with correct topology configuration.

How to reproduce it (minimal and precise):

  1. Deploy Rook-Ceph cluster with CephFS enabled.
  2. Create a StorageClass rook-cephfs with volumeBindingMode: WaitForFirstConsumer and allowedTopologies set to topology.kubernetes.io/zone=default.
  3. Create a PVC referencing rook-cephfs StorageClass in the kuboard namespace.
  4. Observe PVC events showing the topology error.

File(s) to submit:

  • StorageClass YAML (rook-cephfs):
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: rook-cephfs
provisioner: rook-ceph.cephfs.csi.ceph.com
parameters:
  clusterID: rook-ceph
  fsName: myfs
  csi.storage.k8s.io/provisioner-secret-name: rook-csi-cephfs-provisioner
  csi.storage.k8s.io/provisioner-secret-namespace: rook-ceph
  csi.storage.k8s.io/controller-expand-secret-name: rook-csi-cephfs-provisioner
  csi.storage.k8s.io/controller-expand-secret-namespace: rook-ceph
  csi.storage.k8s.io/node-stage-secret-name: rook-csi-cephfs-node
  csi.storage.k8s.io/node-stage-secret-namespace: rook-ceph
reclaimPolicy: Delete
allowVolumeExpansion: true
volumeBindingMode: Immediate
mountOptions:
  # uncomment the following line for debugging
  #- debug

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 29 (13 by maintainers)

Most upvoted comments

Thank you very much! This problem has been solved! However, I encountered a new issue while using Ceph. When I first deployed the cluster.yaml file, all the PODs were running normally. But, if I ran kubectl delete -f cluster.yaml and then ran kubectl apply -f cluster.yaml again, my osd pod would not be created. What’s the reason for this? There are no logs showing anything.

You’re welcome!

Regarding the new issue,kubectl delete -f cluster.yaml would leave leftovers. I would suggest you to follow the cleanup guide https://rook.io/docs/rook/latest-release/Getting-Started/ceph-teardown/. Or @parth-gr could be right person to answer this.