Lssci used on RHEL CoreOS but not installed

[Numblesix]

Describe the bug I noticed today that Trident 22.10 uses lsscsi (maybe even before that) but RHEL CoreOS Nodes dont have this binary installed neither is it possible to install it on those nodes. Sofar i have not noticed any issues on my Cluster (3 so far) but i think it could be confusing a lot of users while searching for errors (thats how i stumbeled upon it).

Environment Non-prod Env, big Netapp Customer in Germany

• Trident version: 22.10
• Trident installation flags used: no autosupport and no debug
• Container runtime: OCP 4.11 with Crio
• Kubernetes version: 1.24
• Kubernetes orchestrator: OCP 4.11
• Kubernetes enabled feature gates: N/A
• OS: only RHEL CoreOS 4.11
• NetApp backend types: ONTAP
• Other:

To Reproduce Check logs of various trident pods

Expected behavior No errors as this should be "expected" on RHEL CoreOS

Additional context

time="2022-12-21T12:46:27Z" level=warning msg="Could not find any devices " requestID=6876b73d-264b-4dcf-9e5d-af879914acf1 requestSource=CSI
time="2022-12-21T12:46:27Z" level=warning msg="Could not run lsscsi: exit status 2" requestID=6876b73d-264b-4dcf-9e5d-af879914acf1 requestSource=CSI
time="2022-12-21T12:46:27Z" level=warning msg="Could not run lsscsi -t: exit status 2" requestID=6876b73d-264b-4dcf-9e5d-af879914acf1 requestSource=CSI

[gnarl]

Hi @Numblesix, we test with OCP and have not run into this issue. Also, we haven't received confirmation from another customer that they have encountered this issue. Is there any customization done with your OCP 4.11 configuration?

[Numblesix]

Hi @gnarl ,

have you checked on RHEL CoreOS Nodes ? I just checked one of my Clusters again and can see the error again.

Could not run lsscsi: exit status 2

[core@osr2infra02 ~]$ cat /etc/redhat-release
Red Hat Enterprise Linux CoreOS release 4.11

[Numblesix]

No to my Information its a pretty basic OCP Cluster with no Modification that should effect something like this

[bromaniac]

I see the same in our cluster:

time="2023-02-21T20:20:07Z" level=warning msg="Could not run lsscsi -t: exit status 2" requestID=123f9165-9fba-4c9d-8576-ca3cf3fa1364 requestSource=CSI

Trident version: 22.10 Container runtime: OCP 4.10 with Crio Kubernetes version: 1.23 Kubernetes orchestrator: OCP 4.10 Kubernetes enabled feature gates: N/A OS: RHEL CoreOS NetApp backend types: ONTAP Select Other:

[uberspot]

We seem to be hitting the same issue on Openshift 4.9. Trident can be updated up to 22.04 but 22.07 fails to start the daemonset and the upgrade stops there.

[gnarl]

Hi @uberspot,

Trident uses the lsscsi binary to collect information that is useful when debugging iSCSI related issues. This binary isn't available in CoreOS but does not prevent Trident from functioning correctly. If Trident is failing to start it is for a reason other than the lsscsi binary being present.

You may want to review the troubleshooting section of the Trident documentation. If you are still unable to determine why your install is failing please contact NetApp support.