You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node(s) CPU architecture, OS, and Version:
Ubuntu 24.04, Any OS
Cluster Configuration:
Single node
Describe the bug:
While running kubectl, it logs an error with
~$ kubectl get nodes
E0829 18:07:08.482306 3622 metrics.go:340] "failed to initialize nfacct client" err="nfacct sub-system not available"
E0829 18:07:08.482414 3622 metrics.go:340] "failed to initialize nfacct client" err="nfacct sub-system not available"
NAME STATUS ROLES AGE VERSION
ip-172-31-8-251 Ready control-plane,master 42s v1.31.0-rc1+k3s1
Steps To Reproduce:
Install k3s
Run kubectl
Expected behavior:
No error should be logged on console
Actual behavior:
Even though the functionality is not affected we do not expect to see these logs
The text was updated successfully, but these errors were encountered:
Environmental Info:
v1.31.0-rc1+k3s1
Node(s) CPU architecture, OS, and Version:
Ubuntu 24.04, Any OS
Cluster Configuration:
Single node
Describe the bug:
While running kubectl, it logs an error with
Steps To Reproduce:
Expected behavior:
No error should be logged on console
Actual behavior:
Even though the functionality is not affected we do not expect to see these logs
The text was updated successfully, but these errors were encountered: