Open MaxDiOrio opened 6 years ago
@niusmallnan I reproduced this issue.
I did the same thing on the ubuntu system, and the reboot won't have any effect.
@rootwuj Is there still a problem switching to the Ubuntu console? I suspect that it is caused by the default console cleanup data after reboot.
@niusmallnan Yeah, I am testing on the ubuntu console. I will have this issue when I reboot node.
Have been facing the same issue on proxmox vms.
Hi @mshivanna I can't reproduce it, Can you give more detailed steps?
Rancher OS amd64 4.14.32-rancher2 RancherOS v1.4.0 VMWare
Sometimes NFS volumes mount perfectly fine, other times...
If I set a mount option of nolock on the volume:
This is after rebooting the worker node as well. Two other pods with PVC's on the same NFS export are working well.
I was able to successfully bring up the PVC (read/write many) on the pod once. I then tried to scale out and add a node, then got the above error on the second pod. After trying to scale back, it hung on deleting the pod - I had to manually kill it. I then rebooted the worker node and got the first error immediately upon restart.
Doing a mount and grepping for the volume shows nothing mounted.
Trying to mount it from the command line fails with permission denied or
Any ideas? This doesn't seem like a usable option for persistent storage right now.