在WSL2中使用device=docker安装lognhorn时iscsid永远会因为sendmsg: bug? ctrl_fd 5错误中止

[pengln]

重现问题所需的命令：
当使用longhorn创建一个pvc, 并在pod中使用该pvc时, 会永远无法分配到分区, 检查问题是iscsid在启动后会因为错误中止

失败的命令的完整输出：

× iscsid.service - iSCSI initiator daemon (iscsid)
Loaded: loaded (/lib/systemd/system/iscsid.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2024-08-11 09:15:05 UTC; 349ms ago
TriggeredBy: ○ iscsid.socket
Docs: man:iscsid(8)
Process: 35037 ExecStartPre=/lib/open-iscsi/startup-checks.sh (code=exited, status=0/SUCCESS)
Process: 35040 ExecStart=/sbin/iscsid (code=exited, status=0/SUCCESS)
Main PID: 35042 (code=exited, status=255/EXCEPTION)

Aug 11 09:15:04 minikube-m02 systemd[1]: Starting iSCSI initiator daemon (iscsid)...
Aug 11 09:15:04 minikube-m02 iscsid[35040]: iSCSI logger with pid=35041 started!
Aug 11 09:15:04 minikube-m02 systemd[1]: Started iSCSI initiator daemon (iscsid).
Aug 11 09:15:05 minikube-m02 systemd[1]: iscsid.service: Main process exited, code=exited, status=255/EXCEPTION
Aug 11 09:15:05 minikube-m02 iscsid[35041]: iSCSI daemon with pid=35042 started!
Aug 11 09:15:05 minikube-m02 iscsid[35041]: sendmsg: bug? ctrl_fd 5
Aug 11 09:15:05 minikube-m02 systemd[1]: iscsid.service: Failed with result 'exit-code'.

使用的操作系统版本：
使用的Windows10 WSL2
kernel版本是5.15.153.1(根据5.15.153.1-microsoft-standard-WSL2的内核编译开启了ISCSI_TCP模块)

这个ctrl_fd5网上有提到可能和netlink有关, 不知道是否是因为ubuntu 22.04的iscsid服务和这个kernel有兼容性问题. 由于Windows10无法在WSL2中开启KVM, 所以希望能帮忙解决

[liangyuanpeng]

/kind support

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues 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 with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues 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 with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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-sigs/prow repository.