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

[BUG] 自建的TC规则被自动删除 #4858

Open
mengyu0829 opened this issue Dec 20, 2024 · 4 comments
Open

[BUG] 自建的TC规则被自动删除 #4858

mengyu0829 opened this issue Dec 20, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@mengyu0829
Copy link

Kube-OVN Version

v1.12.22

Kubernetes Version

v1.31.1

Operation-system/Kernel Version

[root@paas21 enp1s0]# cat /etc/os-release
NAME="Kylin Linux Advanced Server"
VERSION="V10 (Lance)"
ID="kylin"
VERSION_ID="V10"
PRETTY_NAME="Kylin Linux Advanced Server V10 (Lance)"
ANSI_COLOR="0;31"

Description

TC删除

查看 ovs-ovn日志有如下报错:
2024-12-20T07:21:50.206Z|04107|lflow_cache|INFO|Detected cache inactivity (last active 30003 ms ago): trimming cache
2024-12-20T07:22:00.142Z|04108|netdev_linux|WARN|query enp1s0 class 1:65534 (parent 0:0) failed (No such file or directory)

Steps To Reproduce

如上

Current Behavior

创建TC规则、qdisc、class、filter实现基于服务端口的带宽控制,创建完TC后被自动删除

Expected Behavior

可以正常创建TC规则、qdisc、class、filter实现基于服务端口的带宽控制,不会被自动删除

@mengyu0829 mengyu0829 added the bug Something isn't working label Dec 20, 2024
Copy link

dosubot bot commented Dec 20, 2024

@mengyu0829 你好!我是Dosu,一个可以帮助你解决错误、回答问题,并成为贡献者的机器人。我会帮助你解决问题,等待人类维护者的到来。

Kube-OVN might be automatically managing traffic control (TC) rules, which could lead to the removal of custom rules you set. The SetInterfaceBandwidth function in Kube-OVN is responsible for managing TC rules on network interfaces, and it might be overriding your custom configurations [1].

To address this issue, you can consider the following approaches:

  1. Check Kube-OVN Configurations: Ensure that there are no configurations in Kube-OVN that might conflict with your custom TC rules. Kube-OVN might have default settings that override manual changes.

  2. Persistence Across Restarts: Investigate if Kube-OVN has mechanisms to persist custom TC rules across restarts or reconfigurations. If not, you might need to implement a custom script to reapply your rules after any changes.

  3. Monitor Logs: Keep an eye on specific logs or error messages that might indicate why the TC rules are being removed. The logs you provided show cache inactivity and a warning related to querying the network interface, which might be relevant.

  4. Custom Scripts: As a workaround, consider using custom scripts to reapply your TC rules periodically or after specific events that might trigger their removal.

These steps might help in maintaining your custom TC rules without them being automatically deleted.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@mengyu0829
Copy link
Author

同样的服务器同一个TC规则,在calico的集群中没有被删除,机器人回答的方法试过后不能解决问题

@oilbeater
Copy link
Collaborator

enp1s0 是桥接到 ovs 里的网卡么,如果是的话 ovs 会接管 tc 规则

@mengyu0829
Copy link
Author

enp1s0 是桥接到 ovs 里的网卡么,如果是的话 ovs 会接管 tc 规则

enp1s0是k8s的集群网,应该没有桥接到ovs里吧,用kubectl ko vsctl node152 list br 没有查到br-enp1s0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants