Comments (8)
Hi @LordNoteworthy could you check the logs of pod, using this command:
kubectl logs --previous <pod>
from nfs-ganesha-server-and-external-provisioner.
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
from nfs-ganesha-server-and-external-provisioner.
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
from nfs-ganesha-server-and-external-provisioner.
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
from nfs-ganesha-server-and-external-provisioner.
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
from nfs-ganesha-server-and-external-provisioner.
@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 closedYou 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.
from nfs-ganesha-server-and-external-provisioner.
I am still having issues running this, can anyone please help.
@kvaps I don't see any errors displayed for the previous run:
from nfs-ganesha-server-and-external-provisioner.
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 ?
from nfs-ganesha-server-and-external-provisioner.
Related Issues (20)
- Changing mountOptions HOT 5
- Wanting to maintain this if possible HOT 2
- k8s.gcr.io registiry will be frozen by 3rdApr-2023 HOT 4
- Issues when using more replicas! HOT 7
- Failed pull image (Helm chart) HOT 3
- nfs storage size modification impact HOT 6
- Performance issue on NFS provisioner 4.08 HOT 4
- v4.0.8 tag is missing HOT 6
- Extend the disk size of NFS share HOT 7
- Replace deprecated `set-output` command with environment file
- Issue with getting latest version of nfs-server-provisioner chart HOT 4
- How to specify namespace when installing nfs-server-provisioner as sub-chart HOT 7
- How to export and mount pvc for nfs-ganesha to different cluster pv and pvc HOT 5
- Pods stucks sometime in Terminating status HOT 5
- Question: Backing up data by NFS - permission issues? HOT 1
- ESTALE 116 Error HOT 4
- Unable to add labels to nfs-server-provisioner pod when installed as helm subchart HOT 4
- Issue with nfs-ganesha-server-and-external-provisioner HOT 4
- Extremely poor perfomance with WSL2/Docker Desktop/k8s HOT 2
- Is Project maintained? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nfs-ganesha-server-and-external-provisioner.