New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The created SC cannot be used #735
Comments
If you were upgraded from |
Deployment
|
Pod message
|
Let me test locally and get back to you |
Can you describe the PVC? @jieshiyeskey Also the logs from directpv pods running in this node |
|
|
we need the logs from
|
|
Is this the complete log? Can you restart the workload pod once - |
I don't see stage volume call made by k8s. Lets check once more by deleting the pods. |
Just a second. I'm gonna clean up the environment |
|
➜ directpv git:(devel) ✗ kubectl apply -f test.yaml
statefulset.apps/redis-m created
➜ directpv git:(devel) ✗ kubectl get pods
NAME READY STATUS RESTARTS AGE
redis-m-0 1/1 Running 0 39s
➜ directpv git:(devel) ✗ kubectl get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
redisdata-redis-m-0 Bound pvc-ab5ae7c0-484b-41ba-93e5-72dff7bab0ea 500Mi RWO directpv-min-io 40s
➜ directpv git:(devel) ✗ kubectl get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
pvc-ab5ae7c0-484b-41ba-93e5-72dff7bab0ea 500Mi RWO Delete Bound default/redisdata-redis-m-0 directpv-min-io 41s
➜ directpv git:(devel) ✗ kubectl directpv list drives
┌────────────────────────────────┬──────┬───────────┬─────────┬─────────┬─────────┬────────┐
│ NODE │ NAME │ MAKE │ SIZE │ FREE │ VOLUMES │ STATUS │
├────────────────────────────────┼──────┼───────────┼─────────┼─────────┼─────────┼────────┤
│ praveen-thinkpad-x1-carbon-6th │ dm-1 │ vg0-lv--1 │ 800 MiB │ 294 MiB │ 1 │ Ready │
│ praveen-thinkpad-x1-carbon-6th │ dm-0 │ vg0-lv--0 │ 800 MiB │ 794 MiB │ - │ Ready │
│ praveen-thinkpad-x1-carbon-6th │ dm-2 │ vg0-lv--2 │ 800 MiB │ 794 MiB │ - │ Ready │
│ praveen-thinkpad-x1-carbon-6th │ dm-3 │ vg0-lv--3 │ 800 MiB │ 794 MiB │ - │ Ready │
└────────────────────────────────┴──────┴───────────┴─────────┴─────────┴─────────┴────────┘
➜ directpv git:(devel) ✗ kubectl directpv list volumes
┌──────────────────────────────────────────┬──────────┬────────────────────────────────┬───────┬───────────┬──────────────┬─────────┐
│ VOLUME │ CAPACITY │ NODE │ DRIVE │ PODNAME │ PODNAMESPACE │ STATUS │
├──────────────────────────────────────────┼──────────┼────────────────────────────────┼───────┼───────────┼──────────────┼─────────┤
│ pvc-ab5ae7c0-484b-41ba-93e5-72dff7bab0ea │ 500 MiB │ praveen-thinkpad-x1-carbon-6th │ dm-1 │ redis-m-0 │ default │ Bounded │
└──────────────────────────────────────────┴──────────┴────────────────────────────────┴───────┴───────────┴──────────────┴─────────┘
➜ directpv git:(devel) ✗ kubectl directpv info
┌──────────────────────────────────┬──────────┬───────────┬─────────┬────────┐
│ NODE │ CAPACITY │ ALLOCATED │ VOLUMES │ DRIVES │
├──────────────────────────────────┼──────────┼───────────┼─────────┼────────┤
│ • praveen-thinkpad-x1-carbon-6th │ 3.1 GiB │ 500 MiB │ 1 │ 4 │
└──────────────────────────────────┴──────────┴───────────┴─────────┴────────┘
500 MiB/3.1 GiB used, 1 volumes, 4 drives
➜ directpv git:(devel) ✗ kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.1", GitCommit:"8f94681cd294aa8cfd3407b8191f6c70214973a4", GitTreeState:"clean", BuildDate:"2023-01-18T15:58:16Z", GoVersion:"go1.19.5", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.3", GitCommit:"9e644106593f3f4aa98f8a84b23db5fa378900bd", GitTreeState:"clean", BuildDate:"2023-03-15T13:33:12Z", GoVersion:"go1.19.7", Compiler:"gc", Platform:"linux/amd64"}
➜ directpv git:(devel) ✗ kubectl directpv --version
directpv version v4.0.1
➜ directpv git:(devel) ✗ I couldn't reproduce this locally @jieshiyeskey |
can you delete the redis pod once? @jieshiyeskey |
It looks like you have local issue. |
ok.
|
Now can you get the logs from DirectPV pod? @jieshiyeskey |
|
can you get the output of |
|
can you get the output of this? @jieshiyeskey |
|
This is the problem. Looks like your kubelet root-dir is custom or messed up. DirectPV works with |
[root@cn-cp-1 ~]# ls -l /var/lib/kubelet |
DirectPV doesn't follow symlinks while checking mounts as it is non-standard |
I see. Thank you very much. Welcome to China in your spare time. Experience China. |
this PR #737 might help here.. to use custom root dir @jieshiyeskey |
Sure! :) |
Excuse me, is this fixed? If you change kubelet root-dir, will DirectPV works automatically adapt? |
No, It won't automatically adapt. You need to set btw, this is not yet released. Stay tuned for the next release.. |
example: Like this?
|
OK |
Basic information
kubernetes-v1.26.3
directpv version v4.0.1
Test example
** Result**
Logs
Problem
The preceding information is displayed to keep the pod in the ContainerCreating state. Previous directpv version has also been saved this problem, please master to check, thanks.
The text was updated successfully, but these errors were encountered: