Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Unable to provision trident in Rancher OS based k8s cluster
2019-07-03
05:20 AM
2,103 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi!
I'm trying to install trident on a Rancher provided k8s cluster but fails with the following error:
/opt/rke/var/lib/kubelet/pods/057a897a-9d89-11e9-9490-005056bf9b18/volumes/kubernetes.io~nfs/trident Output: mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
Rancher OS running on the worker nodes is v1.5.1 and the
volume-nfs
has been enabled on the worker nodes, albeit with no success - the tridentctl install command fails with the above error.
What do I need to do on the worker nodes in order to have this working.
Cheers
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks like rpcbind might not be running or isn't installed - can you share the output of the "chkconfig --list rpcbind" and "service rpcbind status" commands?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When you said you enabled volumes-nfs on the worker nodes, what did you mean? I'm having a whale of a time getting any NFS or Trident shares to work as a storage class with a Rancher OS based k8s cluster. I was able to install trident without that error on my cluster, I just can't provision storage.
