mayastor: pv provisioning fails with "error generating accessibility requirements: no available topology found"

Describe the bug Installed OpenEBS Mayastor via helm using the official doc, the pods run and do not throw any obvious errors:

kubectl get pods -n openebs

NAME                                           READY   STATUS    RESTARTS   AGE
openebs-agent-core-5567874b6-hddg4             2/2     Running   0          31m
openebs-agent-ha-node-54lxd                    1/1     Running   0          31m
openebs-agent-ha-node-spzkr                    1/1     Running   0          31m
openebs-agent-ha-node-vx25g                    1/1     Running   0          31m
openebs-agent-ha-node-zrnbp                    1/1     Running   0          31m
openebs-api-rest-6dc4564f6b-mw7f9              1/1     Running   0          31m
openebs-csi-controller-5676f6758-wprdk         5/5     Running   0          31m
openebs-csi-node-bclqc                         2/2     Running   0          31m
openebs-csi-node-qglkr                         2/2     Running   0          31m
openebs-csi-node-vrlkq                         2/2     Running   0          31m
openebs-csi-node-z86vr                         2/2     Running   0          31m
openebs-etcd-0                                 1/1     Running   0          31m
openebs-etcd-1                                 1/1     Running   0          31m
openebs-etcd-2                                 1/1     Running   0          31m
openebs-io-engine-4pjx8                        2/2     Running   0          31m
openebs-io-engine-9ffwf                        2/2     Running   0          31m
openebs-io-engine-hrnl7                        2/2     Running   0          31m
openebs-io-engine-zvfm4                        2/2     Running   0          31m
openebs-localpv-provisioner-748468b4d5-lr8q7   1/1     Running   0          31m
openebs-nats-0                                 3/3     Running   0          31m
openebs-nats-1                                 3/3     Running   0          31m
openebs-nats-2                                 3/3     Running   0          31m
openebs-operator-diskpool-56c7bf678f-lg4cn     1/1     Running   0          31m

diskpool seems to work:

kubectl get diskpool -n openebs
NAME    NODE                     STATE     POOL_STATUS   CAPACITY      USED   AVAILABLE
test1   vmi-ctrinfratest02w004   Created   Online        53632565248   0      53632565248

storageclass is defined:

 kubectl get storageclass mayastor-1
NAME                   PROVISIONER               RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE
mayastor-1 (default)   io.openebs.csi-mayastor   Delete          Immediate           false                  20h

when I try to add a pvc , a pv is not provisioned:

Name:          ms-volume-claim
Namespace:     default
StorageClass:  mayastor-1
Status:        Pending
Volume:
Labels:        <none>
Annotations:   volume.beta.kubernetes.io/storage-provisioner: io.openebs.csi-mayastor
               volume.kubernetes.io/storage-provisioner: io.openebs.csi-mayastor
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Used By:       <none>
Events:
  Type     Reason                Age                   From                                                                                 Message
  ----     ------                ----                  ----                                                                                 -------
  Normal   Provisioning          47m (x9 over 51m)     io.openebs.csi-mayastor_vmi-ctrinfratest02w004_8b843196-d04d-49b5-99db-382a98a77ca1  External provisioner is provisioning volume for claim "default/ms-volume-claim"
  Warning  ProvisioningFailed    47m (x9 over 51m)     io.openebs.csi-mayastor_vmi-ctrinfratest02w004_8b843196-d04d-49b5-99db-382a98a77ca1  failed to provision volume with StorageClass "mayastor-1": error generating accessibility requirements: no available topology found
  Normal   Provisioning          4m23s (x15 over 32m)  io.openebs.csi-mayastor_vmi-ctrinfratest02w004_0c49a781-05c6-402a-a2d3-536c399f08dc  External provisioner is provisioning volume for claim "default/ms-volume-claim"
  Warning  ProvisioningFailed    4m23s (x15 over 32m)  io.openebs.csi-mayastor_vmi-ctrinfratest02w004_0c49a781-05c6-402a-a2d3-536c399f08dc  failed to provision volume with StorageClass "mayastor-1": error generating accessibility requirements: no available topology found
  Normal   ExternalProvisioning  59s (x203 over 51m)   persistentvolume-controller                                                          waiting for a volume to be created, either by external provisioner "io.openebs.csi-mayastor" or manually created by system administrator

To Reproduce Steps to reproduce the behavior: Install using official Guide https://openebs.io/docs/user-guides/mayastor https://mayastor.gitbook.io/introduction/quickstart/configure-mayastor

About this issue

  • Original URL
  • State: closed
  • Created 10 months ago
  • Comments: 41 (17 by maintainers)

Most upvoted comments

alright, after setting the following in the values yaml:

mayastor:
  csi:
    node:
      kubeletDir: "/var/lib/k0s/kubelet/"

it works finally!

restated the csi-node pods, re-deployed it completely with helm, also rebootet the nodes themself - no change unfortunatly