-
Notifications
You must be signed in to change notification settings - Fork 136
Open
Labels
kind/bugkind/failing-testCategorizes issue or PR as related to a failing test.Categorizes issue or PR as related to a failing test.
Description
What happened:
The reporter in the kubevirt/kubevirt testsuite tries to run lsfd as part of collecting information about the test environment on a given node. It looks like recent kubevirtci nodes (1.34) are missing this binary.
This output can be observed in the console:
failed to execute command [sh -c lsfd --summary] on node01, stdout: , stderr: sh: line 1: lsfd: command not found
What you expected to happen:
The kubevirt test suite should be able to collection information successfully.
How to reproduce it (as minimally and precisely as possible):
Run make functest on kubevirt/kubevirt main.
Additional context:
Add any other context about the problem here.
Environment:
- KubeVirt version (use
virtctl version): N/A - Kubernetes version (use
kubectl version): N/A - VM or VMI specifications: N/A
- Cloud provider or hardware configuration: N/A
- OS (e.g. from /etc/os-release): N/A
- Kernel (e.g.
uname -a): N/A - Install tools: N/A
- Others: N/A
dosubot and dhiller
Metadata
Metadata
Assignees
Labels
kind/bugkind/failing-testCategorizes issue or PR as related to a failing test.Categorizes issue or PR as related to a failing test.