Skip to content
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

Frequent "error querying ethtool ioctl link state" in talos logs #9296

Closed
Tracked by #8484
jfroy opened this issue Sep 10, 2024 · 2 comments · Fixed by #9302
Closed
Tracked by #8484

Frequent "error querying ethtool ioctl link state" in talos logs #9296

jfroy opened this issue Sep 10, 2024 · 2 comments · Fixed by #9302
Assignees

Comments

@jfroy
Copy link
Contributor

jfroy commented Sep 10, 2024

Bug Report

Description

In v1.8.0-beta.0, I am now seeing this somewhat regular talos log line:

[talos] error querying ethtool ioctl link state {"component": "controller-runtime", "controller": "network.LinkStatusController", "link": "<LINK>", "error": "no such device"}

This appears to be logged shortly following this kernel log line:

eth0: renamed from tmp<random>

which I believe comes from cilium's normal operations.

The output of talosctl get linkstatus looks OK, so this may be a race when an interface gets renamed that resolves itself.

Environment

  • Talos version:
    Client:
            Tag:         v1.7.6
            SHA:         ae67123a
            Built:       
            Go version:  go1.22.5
            OS/Arch:     linux/amd64
    Server:
            NODE:        192.168.1.13
            Tag:         v1.8.0-beta.0
            SHA:         b92c2e49
            Built:       
            Go version:  go1.22.7
            OS/Arch:     linux/amd64
            Enabled:     RBAC
    
  • Kubernetes version:
    Client Version: v1.31.0
    Kustomize Version: v5.4.2
    Server Version: v1.31.0
    
  • Platform: baremetal
  • Kernel: custom 6.10.6 configuration

I've attached a support file.

@smira
Copy link
Member

smira commented Sep 10, 2024

These are harmless, but we should silence them

@smira smira self-assigned this Sep 10, 2024
@Syntax3rror404
Copy link

eth0: renamed from tmp

Could be the CNI which is normal.

smira added a commit to smira/talos that referenced this issue Sep 11, 2024
We should ignore this, it's a totally an optional feature used in
containers (Talos on its own kernel has ethtool-netlink).

Fixes siderolabs#9296

Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
smira added a commit to smira/talos that referenced this issue Sep 13, 2024
We should ignore this, it's a totally an optional feature used in
containers (Talos on its own kernel has ethtool-netlink).

Fixes siderolabs#9296

Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
(cherry picked from commit a9269ac)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants