-
Notifications
You must be signed in to change notification settings - Fork 27
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
pvc dont mount to pod #197
Comments
And another moment, if I do ┊ pvc-47dde43d-3385-4810-b181-d9d498022e9a ┊ aisk8swr01t ┊ 7033 ┊ ┊ ┊ Unknown ┊ ┊
┊ pvc-47dde43d-3385-4810-b181-d9d498022e9a ┊ pve-1 ┊ 7033 ┊ Unused ┊ ┊ Unknown ┊ 2023-05-03 10:34:07 ┊
┊ pvc-47dde43d-3385-4810-b181-d9d498022e9a ┊ pve-2 ┊ 7033 ┊ Unused ┊ ┊ Unknown ┊ 2023-05-03 10:33:53 ┊ |
Seems that DRBD is not set up correctly on the k8s nodes. Please check "linstor node info" and verify that DRBD is actually supported on the k8s nodes. You might also verify that DRBD 9 is loaded instead of 8.4 by checking /proc/drbd on the k8s nodes. |
root@pve-3:~# linstor node info
╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
┊ Node ┊ Diskless ┊ LVM ┊ LVMThin ┊ ZFS/Thin ┊ File/Thin ┊ SPDK ┊ EXOS ┊ Remote SPDK ┊ Storage Spaces ┊ Storage Spaces/Thin ┊
╞══════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╡
┊ aisk8swr01t ┊ + ┊ + ┊ + ┊ - ┊ + ┊ - ┊ - ┊ + ┊ - ┊ - ┊
┊ aisk8swr02t ┊ + ┊ + ┊ + ┊ - ┊ + ┊ - ┊ - ┊ + ┊ - ┊ - ┊
┊ aisk8swr03t ┊ + ┊ + ┊ + ┊ - ┊ + ┊ - ┊ - ┊ + ┊ - ┊ - ┊
┊ pve-1 ┊ + ┊ + ┊ + ┊ + ┊ + ┊ - ┊ - ┊ + ┊ - ┊ - ┊
┊ pve-2 ┊ + ┊ + ┊ + ┊ + ┊ + ┊ - ┊ - ┊ + ┊ - ┊ - ┊
┊ pve-3 ┊ + ┊ + ┊ + ┊ + ┊ + ┊ - ┊ - ┊ + ┊ - ┊ - ┊
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─────────────────────────────────────────────────────────────────────────────────────╮
┊ Node ┊ DRBD ┊ LUKS ┊ NVMe ┊ Cache ┊ BCache ┊ WriteCache ┊ OpenFlex ┊ Storage ┊
╞═════════════════════════════════════════════════════════════════════════════════════╡
┊ aisk8swr01t ┊ + ┊ + ┊ - ┊ + ┊ + ┊ + ┊ - ┊ + ┊
┊ aisk8swr02t ┊ + ┊ + ┊ - ┊ + ┊ + ┊ + ┊ - ┊ + ┊
┊ aisk8swr03t ┊ + ┊ + ┊ - ┊ + ┊ + ┊ + ┊ - ┊ + ┊
┊ pve-1 ┊ + ┊ + ┊ + ┊ + ┊ + ┊ + ┊ + ┊ + ┊
┊ pve-2 ┊ + ┊ + ┊ + ┊ + ┊ + ┊ + ┊ + ┊ + ┊
┊ pve-3 ┊ + ┊ + ┊ + ┊ + ┊ + ┊ + ┊ + ┊ + ┊
╰─────────────────────────────────────────────────────────────────────────────────────╯ k8s node root@aisk8swr01t:~# cat /proc/drbd
version: 9.2.3 (api:2/proto:86-122)
GIT-hash: c142ca1280c41aee1330b980544ef276330ff6ef build by root@aisk8swr01t, 2023-05-02 12:21:51
Transports (api:18): tcp (9.2.3) VM and their disk deploy at servers with linstor cluster |
It should work, but something is blocking the LINSTOR Satellite on the k8s node from setting up the DRBD device. Are there any error reports related to the resource ( |
|
Seems like the issue is:
I believe LINSTOR should automatically select the right verify algorithm useable by all nodes. What kind of kernels / host OS are you using? Seems like you use very different versions that might not have any algorithms in common. |
i upgrade kernel on k8s nodes to 5.15.104, the same version on linstor cluster root@aisk8swr01t:~# modprobe drbd
root@aisk8swr01t:~# cat /proc/drbd
version: 8.4.11 (api:1/proto:86-101)
srcversion: 98E710E58B3041F3046305B
root@aisk8swr01t:~# apt list --installed | grep drbd
drbd-dkms/unknown,now 9.2.3-1 all [installed]
drbd-utils/unknown,now 9.23.1-1 amd64 [installed] |
You can try running |
I brought to the same version of the kernel and drbd on all nodes kubectl describe
root@pve-3:/etc/apt# linstor v l -r pvc-3f8cb1b6-a1d6-4bb9-9bc2-dcd46fd87385
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
┊ Node ┊ Resource ┊ StoragePool ┊ VolNr ┊ MinorNr ┊ DeviceName ┊ Allocated ┊ InUse ┊ State ┊
╞═════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╡
┊ aisk8swr02t ┊ pvc-3f8cb1b6-a1d6-4bb9-9bc2-dcd46fd87385 ┊ DfltDisklessStorPool ┊ 0 ┊ 1033 ┊ None ┊ ┊ Unused ┊ Diskless ┊
┊ pve-1 ┊ pvc-3f8cb1b6-a1d6-4bb9-9bc2-dcd46fd87385 ┊ drbdhddpool1 ┊ 0 ┊ 1033 ┊ /dev/drbd1033 ┊ 261 KiB ┊ Unused ┊ UpToDate ┊
┊ pve-2 ┊ pvc-3f8cb1b6-a1d6-4bb9-9bc2-dcd46fd87385 ┊ drbdhddpool1 ┊ 0 ┊ 1033 ┊ /dev/drbd1033 ┊ 279 KiB ┊ Unused ┊ UpToDate ┊
┊ pve-3 ┊ pvc-3f8cb1b6-a1d6-4bb9-9bc2-dcd46fd87385 ┊ DfltDisklessStorPool ┊ 0 ┊ 1033 ┊ /dev/drbd1033 ┊ ┊ ┊ Unknown ┊
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
root@pve-3:/etc/apt# linstor r l -r pvc-3f8cb1b6-a1d6-4bb9-9bc2-dcd46fd87385
╭───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
┊ ResourceName ┊ Node ┊ Port ┊ Usage ┊ Conns ┊ State ┊ CreatedOn ┊
╞═══════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╡
┊ pvc-3f8cb1b6-a1d6-4bb9-9bc2-dcd46fd87385 ┊ aisk8swr02t ┊ 7033 ┊ Unused ┊ Ok ┊ Diskless ┊ ┊
┊ pvc-3f8cb1b6-a1d6-4bb9-9bc2-dcd46fd87385 ┊ pve-1 ┊ 7033 ┊ Unused ┊ Connecting(aisk8swr02t) ┊ UpToDate ┊ 2023-05-03 12:24:18 ┊
┊ pvc-3f8cb1b6-a1d6-4bb9-9bc2-dcd46fd87385 ┊ pve-2 ┊ 7033 ┊ Unused ┊ Connecting(aisk8swr02t) ┊ UpToDate ┊ 2023-05-03 12:23:39 ┊
┊ pvc-3f8cb1b6-a1d6-4bb9-9bc2-dcd46fd87385 ┊ pve-3 ┊ 7033 ┊ ┊ Ok ┊ DELETING ┊ 2023-05-03 12:23:40 ┊
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
|
This error might be of interest for https://github.com/linbit/linstor-server |
Hi.
I deploy linstor-csi-1.19 (try 1.17 too) in my k8s cluster
Add workers in linstor cluster
I create storage-class and pvc
PVC is created, then I see 'linstor v l' and pvc has status upToDate
BUT, i create pod with pvc and i have a problem,
In pods logs i see the following
In second pod
But I also tried to create a pod with 1 replication, the same error with mounting
Status also changed in linstor
my manifests
The text was updated successfully, but these errors were encountered: