Network attributes error logs when using Talos OS

[aivanov-citc]

We use Talos as the operating system for kubernetes. NFD logs constantly show errors related to the network attributes of bonding_masters.

What happened:

E0819 06:20:51.415724       1 network.go:154] "failed to read net iface attribute" err="open /host-sys/class/net/bonding_masters/operstate: not a directory" attributeName="operstate"
E0819 06:20:51.415775       1 network.go:154] "failed to read net iface attribute" err="open /host-sys/class/net/bonding_masters/speed: not a directory" attributeName="speed"
I0819 06:20:51.816548       1 nfd-worker.go:664] "starting feature discovery..."
I0819 06:20:51.816977       1 nfd-worker.go:677] "feature discovery completed"

What you expected to happen:
Can you fix it so that this interface is ignored during scanning

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version): v1.30.3
• OS (e.g: cat /etc/os-release): Talos 1.7.6
• Kernel (e.g. uname -a): 6.6.43-talos

[marquiz]

@aivanov-citc thanks for reporting the issue. Yes, I think we should ignore the bonding_masters "iface". The error itself is harmless even if annoying and distractive.
/help

[k8s-ci-robot]

@marquiz:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

@aivanov-citc thanks for reporting the issue. Yes, I think we should ignore the bonding_masters "iface". The error itself is harmless even if annoying and distractive.
/help

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.