-
Notifications
You must be signed in to change notification settings - Fork 25
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
Cannot mount provisioned block device #234
Comments
Better to check disk inside the container (pod) Controller done the job: CreateVolume: volume created
ControllerPublishVolume: volume published Node plugin done the job too: Disk successfully formatted (mkfs): xfs - /dev/sdb /var/lib/k0s/kubelet/plugins/kubernetes.io/csi/csi.proxmox.sinextra.dev/8df3edcea3bfd50f034ba05a0290386aa203bc4fcdb1325cc75005c52fb9fe2d/globalmount
Mounting cmd (mount) with arguments (-t xfs -o bind,remount,rw /var/lib/k0s/kubelet/plugins/kubernetes.io/csi/csi.proxmox.sinextra.dev/8df3edcea3bfd50f034ba05a0290386aa203bc4fcdb1325cc75005c52fb9fe2d/globalmount /var/lib/k0s/kubelet/pods/383d7e80-ec16-41a7-b0e7-152b9eb30af5/volumes/kubernetes.io~csi/pvc-cf3b9e48-cb59-4212-947a-d42c5c9972e5/mount) the disk should be here /var/lib/k0s/kubelet/pods/383d7e80-ec16-41a7-b0e7-152b9eb30af5/volumes/kubernetes.io~csi/pvc-cf3b9e48-cb59-4212-947a-d42c5c9972e5/mount Unfortunately, I do not have experience with k0s, I cannot say exactly how to find the disk on the host. |
Thanks for the answer, but the volume is in fact not mounted. The pod will start and the container can write to that location, but the data will end up on the VMs root filesystem. I am pretty puzzled as to why the CSI driver thinks that the mount succeeded as it clearly did not. It neither mount nor unmounts the disk at all. What it does tho, is formatting it correctly. |
If kubket inside the container, check the hostPath volumes paths.
kubeletDir: /var/lib/k0s/kubelet |
Bug Report
Hey there,
I've got a weird one. I am trying to use your csi driver on k0s and for some reason the mounting part does not work correctly. In the logs there is no mention of a failed mount, but the fact is that when I ssh into my node the disk is not mounted anywhere. The unmounting part does not work as well when I do the mounting manually. Since I am running a RHEL derivate (AlmaLinux) I disabled SELinux to be sure, but I really don't think it causes harm in this case.
Description
This is my deployment:
Logs
Controller: [
kubectl logs -c proxmox-csi-plugin-controller proxmox-csi-plugin-controller-...
]CSI Attacher
Controllerplugin
Node:
Environment
AlmaLinux 9.4 (Seafoam Ocelot)
The text was updated successfully, but these errors were encountered: