NFS Server Provisioner pod keeps restarting about nfs-ganesha-server-and-external-provisioner

[kvaps]

Hi @LordNoteworthy could you check the logs of pod, using this command:

kubectl logs --previous <pod>

[horca]

Same problem here.

My environment:
Fedora 35 - kernel 5.15.7-200
Kind 0.11.1
Docker 20.10.12
Kubernetes client 1.23.1
Kubernetes server 1.21.1
NFS server installed with helm chart https://artifacthub.io/packages/helm/kvaps/nfs-server-provisioner

$ kubectl logs nfs-provisioner-nfs-server-provisioner-0 
I1221 09:42:54.392147       1 main.go:65] Provisioner cluster.local/nfs-provisioner-nfs-server-provisioner specified
I1221 09:42:54.392342       1 main.go:89] Setting up NFS server!

$ kubectl logs --previous nfs-provisioner-nfs-server-provisioner-0 
I1221 09:43:35.419528       1 main.go:65] Provisioner cluster.local/nfs-provisioner-nfs-server-provisioner specified
I1221 09:43:35.420228       1 main.go:89] Setting up NFS server!

$ kubectl describe pod nfs-provisioner-nfs-server-provisioner-0
Name:         nfs-provisioner-nfs-server-provisioner-0
Namespace:    nfs
Priority:     0
Node:         3w-worker/172.19.0.3
Start Time:   Tue, 21 Dec 2021 10:41:54 +0100
Labels:       app=nfs-server-provisioner
              chart=nfs-server-provisioner-1.4.0
              controller-revision-hash=nfs-provisioner-nfs-server-provisioner-64668dc48f
              heritage=Helm
              release=nfs-provisioner
              statefulset.kubernetes.io/pod-name=nfs-provisioner-nfs-server-provisioner-0
Annotations:  <none>
Status:       Running
IP:           10.244.1.2
IPs:
  IP:           10.244.1.2
Controlled By:  StatefulSet/nfs-provisioner-nfs-server-provisioner
Containers:
  nfs-server-provisioner:
    Container ID:  containerd://fd734af57b91226fa1e33e900ab0cd2861ed3e89c3da1be29c044d927d83fd11
    Image:         k8s.gcr.io/sig-storage/nfs-provisioner:v3.0.0
    Image ID:      k8s.gcr.io/sig-storage/nfs-provisioner@sha256:2de1d15fc1f2a33618c61ff8d499ef22a7b2b8961952f059656a245b98498ba4
    Ports:         2049/TCP, 2049/UDP, 32803/TCP, 32803/UDP, 20048/TCP, 20048/UDP, 875/TCP, 875/UDP, 111/TCP, 111/UDP, 662/TCP, 662/UDP
    Host Ports:    0/TCP, 0/UDP, 0/TCP, 0/UDP, 0/TCP, 0/UDP, 0/TCP, 0/UDP, 0/TCP, 0/UDP, 0/TCP, 0/UDP
    Args:
      -provisioner=cluster.local/nfs-provisioner-nfs-server-provisioner
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    137
      Started:      Tue, 21 Dec 2021 10:44:39 +0100
      Finished:     Tue, 21 Dec 2021 10:44:53 +0100
    Ready:          False
    Restart Count:  4
    Environment:
      POD_IP:          (v1:status.podIP)
      SERVICE_NAME:   nfs-provisioner-nfs-server-provisioner
      POD_NAMESPACE:  nfs (v1:metadata.namespace)
    Mounts:
      /export from data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-6rwfl (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  data:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     
    SizeLimit:  <unset>
  kube-api-access-6rwfl:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                  From               Message
  ----     ------     ----                 ----               -------
  Normal   Scheduled  4m23s                default-scheduler  Successfully assigned nfs/nfs-provisioner-nfs-server-provisioner-0 to 3w-worker
  Normal   Pulling    4m22s                kubelet            Pulling image "k8s.gcr.io/sig-storage/nfs-provisioner:v3.0.0"
  Normal   Pulled     4m8s                 kubelet            Successfully pulled image "k8s.gcr.io/sig-storage/nfs-provisioner:v3.0.0" in 13.754935295s
  Normal   Created    98s (x5 over 4m8s)   kubelet            Created container nfs-server-provisioner
  Normal   Started    98s (x5 over 4m8s)   kubelet            Started container nfs-server-provisioner
  Normal   Pulled     98s (x4 over 3m53s)  kubelet            Container image "k8s.gcr.io/sig-storage/nfs-provisioner:v3.0.0" already present on machine
  Warning  BackOff    70s (x9 over 3m38s)  kubelet            Back-off restarting failed container

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages issues and PRs 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

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

This bot triages issues and PRs 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[LordNoteworthy]

I am still having issues running this, can anyone please help.

@kvaps I don't see any errors displayed for the previous run:

[LordNoteworthy]

This seems to happen in Fedora v35 and not in debian based distros. Interesting. Can you please just try to install the helm chart as it is in Fedora ?