-
Notifications
You must be signed in to change notification settings - Fork 253
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
nfd-worker
errors reading speed
parameter for paravirtualized devices
#1556
Comments
Fixed by #1557 |
@marquiz: Closing this issue. In response to this:
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/test-infra repository. |
I'm still seeing this for the local interface
|
@weikinhuang which version of nfd are you running? The fix hasn't been released, yet. It'll be in the upcoming v0.16 release |
@marquiz oh, I thought the fix was in 0.15.2. I am on 0.15.3. If that's the case thanks for letting me know! |
What happened:
The
nfd-worker
pods on my cluster get this error every time they perform feature discovery:I believe this is because the devices are paravirtual and so the
speed
parameter is nonsensical in this context. The file still exists however I think because the kernel puts it there.What you expected to happen:
Feature discovery completes without error
How to reproduce it (as minimally and precisely as possible):
Run feature discovery on a node with paravirtual devices connected
Anything else we need to know?:
N/A
Environment:
kubectl version
): 1.27.7cat /etc/os-release
): Ubuntu 22.04.3 LTSuname -a
): Linux 5.15.0-91-generic 101-Ubuntu SMP Tue Nov 14 13:30:08 UTC 2023 x86_64 x86_64 x86_64 GNU/LinuxThe text was updated successfully, but these errors were encountered: