Comment # 23 on bug 1214540 from Janos Miko

Hello,

I'm not sure if this is related or not, but it seems like the latest nfs-client
update broke the nfs client in some cases.

Context: I'm running multiple Kubernetes clusters on top of OpenSUSE MicroOS
using  the following Terraform module:
https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner

I'm using Rancher Longhorn for volumes in the cluster and Longhorn's RWX
volumes are using nfs under the hood.

Yesterday, a transactional-update scheduled update upgraded all my nodes
(including nfs-client package from 2.6.3-39.4 to 2.6.3-39.5) and the RWX
volumes started to fail.

The error message was the following in the journal:
---
Oct 11 07:42:23 dev-worker-1 k3s[1294]: Mounting command:
/usr/local/sbin/nsmounter
Oct 11 07:42:23 dev-worker-1 k3s[1294]: Mounting arguments: mount -t nfs -o
vers=4.1,noresvport,intr,hard
10.43.207.185:/pvc-13538170-4278-4467-b2b0-1f1ba6f54a4c
/var/lib/kubelet/plugins/kubernetes.io/csi/driver.longhorn.io/185c34f566c2eca6e8c7c6a2ede2094c076d7d25ddae286dc633eeef80551af0/globalmount
Oct 11 07:42:23 dev-worker-1-autoscaled-small-19baf778f50efd8c k3s[1294]:
Output: mount.nfs: Protocol not supported for
10.43.207.185:/pvc-13538170-4278-4467-b2b0-1f1ba6f54a4c on
/var/lib/kubelet/plugin
---

I also enabled debug logging in the kernel, you can find those logs in the
related bug report.

Anyway, after a few hours I decided to use MicroOS rollback going back to the
latest snapshot from 2 days ago and the issue is solved now on that node.

Related bug report on Github:
https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/issues/1016

Please let me know if I can provide you any additional information about this
issue.

Regards,
Janos Miko