Issue 1 with using the server-provisioner on top of mayastor backed storage class

[anmshkmr]

Warning  FailedMount  56s (x10 over 5m7s)  kubelet            MountVolume.MountDevice failed for volume "pvc-c30b58a9-3c42-4c02-9161-d1def78fe08f" : rpc error: code = Internal desc = Failed to stage volume c30b58a9-3c42-4c02-9161-d1def78fe08f: attach failed: IO error: Input/output error (os error 5), args: hostnqn=nqn.2019-05.io.openebs:node-name:m720q3,hostid=3f83c280-4090-11eb-b735-60d30e901b00,nqn=nqn.2019-05.io.openebs:c30b58a9-3c42-4c02-9161-d1def78fe08f,transport=tcp,traddr=192.168.1.113,trsvcid=8420,reconnect_delay=10,ctrl_loss_tmo=1980,nr_io_queues=2

This happens once in a while, apparently when openebs and nfs-server-provisioner pod cannot communicate with each other. To fix it, I had to delete all nfs-server-provisioner resources. However, the pvc’s defined on top of the storage class need to be created again.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale