Open styshoo opened 2 months ago
Hi @styshoo , Can you provide more details on the workflow..
kubectl get sc <sc-name>
kubectl get pvc <pvc-name>
kubectl get lvmvolume <pv-name> -n openebs
Do you mean after restarting lvm-node plugin lv gets created successfully?
What steps did you take and what happened: [A clear and concise description of what the bug is, and what commands you ran.] The lvm csi runs correctly at first. But after a longtime running(maybe two months), I create a StatefulSet with lvm pvc, but the pv can't be created.
What did you expect to happen: PV can be successfully created.
The output of the following commands will help us better understand what's going on: (Pasting long output into a GitHub gist or other Pastebin is fine.) describe pod:
kubectl get pods -n openebs
kubectl get lvmvol -A -o yaml
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.] In the csi node log, if a pv can be successfully created, the log should be as following:
However, in my environment, we only get the lines "Got add event for Vo" and "lvmvolume object to be enqueued by Add handler", without the third line. After I reboot the csi node pod, everything is fine again. I can create pv successfully.
So, I doubt that there is something wrong with the workqueue, LVMVolume is put into the workqueue, but in the
processNextWorkItem
loop, nothing can be get from the queue. But I'm not sure with that, is there a clue ?Environment:
kubectl version
):1.24.1/etc/os-release
):