[BUG] when i confiugred BFD, ECMP ovnext(network namespace) have some problem. #4998
Comments
|
The "Invalid argument" error when executing commands in a network namespace like
If these steps do not resolve the issue, consider reviewing the specific configurations and any recent changes that might have affected the network namespace setup. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other |
================================================
but in my environment have some proble and bugs came up.
cni-9374e2ea-9c78-7101-cc0a-0efc8c98db02 (id: 2)
[root@vnode-117-35 ~]# ip netns list
Error: Peer netns reference is invalid.
Error: Peer netns reference is invalid.
ovnext # it seems the ns is already exist
[root@vnode-117-35 ~]# ip netns exec ovnext bash ip a
setting the network namespace "ovnext" failed: Invalid argument
[root@vnode-117-35 ~]# ip netns exec ovnext bash ip a
setting the network namespace "ovnext" failed: Invalid argument
[root@vnode-117-35 ~]# ip netns exec ovnext ip a
setting the network namespace "ovnext" failed: Invalid argument
[root@vnode-117-35 ~]# ip netns exec ovnext ip a
setting the network namespace "ovnext" failed: Invalid argument
[root@vnode-117-35 ~]# ip netns exec ovnext bash
setting the network namespace "ovnext" failed: Invalid argument
it seems the ns is already exist, but i do not know why you can not exec it |
|
yes I cannot exec the network namespace in the gw nodes. [root@vnode-117-34 ~]# k get nodes --show-labels [root@vnode-117-34 ~]# k get nodes [root@vnode-117-34 ~]# k get provider-network [root@vnode-117-34 ~]# k get vlan listing subnets external subnet. Internal overlay subnet. router 963d12e7-f72f-4d9c-9a0e-1b7c42da7a03 (vpc2) [root@vnode-117-34 ~]# k ko nbctl list bfd _uuid : 2e89a14b-cf2c-4c7e-89c7-a9ad38a935df _uuid : 575551cf-7c64-420a-8d15-a10e0f104698 [root@vnode-117-34 ~]# k ko nbctl find Logical_Router_Static_Route policy=src-ip options=ecmp_symmetric_reply="true" _uuid : 3bda2bc6-4110-48b7-977d-114aac43c55e _uuid : fb7f394a-3d9e-43c1-9db8-1efa4533240a _uuid : cfd0b1ee-d811-4787-9e10-f2489903ffda |
|
In your env: Can you set up a netns and exec into it? like this: https://girondi.net/post/network_namespaces/ |
|
[root@vnode-117-35 ~]# It says already existed and cannot apply exec |
|
please change a name, not use ovnext, just use a new name for your local env test |
|
[root@vnode-117-29 ~]# ip netns add helloworld It works very well in my enviroment to config by my hand. |
|
could you please test this?
|
|
[root@vnode-117-29 ~]# ip netns exec cni-3be0d59d-e577-7099-da25-d79c9578fd8d bash [root@vnode-117-29 ~]# ip netns exec ovnext bash cni pod can be listed but ovnext is not executed. |
|
kubectl exec into the kube-ovn-cni pod, and then, inside the pod, run ip netns exec into the ovnext |
|
Okay It works well. Thank you for your answer. |
|
but I have one more issue _uuid : 2e89a14b-cf2c-4c7e-89c7-a9ad38a935df 10.9.0.1 is the physical gw of public subnet but its status is admin_down. [root@vnode-117-34 ~]# k get cm -n kube-system ovn-external-gw-config -oyaml [root@vnode-117-34 ~]# k get subnet external0 -oyaml apiVersion: kubeovn.io/v1
|
maybe |
|
is it afftected distributed routers in gw nodes?? |
In my opinion, no. but i wonder, why you has a bfd refer to |
|
My servers env's public ip subnet is 10.9.0.0/16 cidr, enable-external-gw: "true" https://kubeovn.github.io/docs/v1.13.x/en/guide/eip-snat/ |
Kube-OVN Version
v.1.13
Kubernetes Version
1.30.9
Operation-system/Kernel Version
"Rocky Linux 8.10 (Green Obsidian)"
Description
https://kube-ovn.readthedocs.io/zh-cn/latest/en/advance/ovn-l3-ha-based-ecmp-with-bfd/
I reference this page and configure BFD, External, Internal subnet and oeip, ofip
and testify the gw node ovnext
something peer network interface has not connected.
Steps To Reproduce
https://kube-ovn.readthedocs.io/zh-cn/latest/en/advance/ovn-eip-fip-snat/
https://kube-ovn.readthedocs.io/zh-cn/latest/en/advance/ovn-l3-ha-based-ecmp-with-bfd/
I referenced these pages.
Current Behavior
[root@vnode-117-35 ~]# ip netns exec ovnext bash ip a
setting the network namespace "ovnext" failed: Invalid argument
[root@vnode-117-35 ~]# ip netns exec ovnext bash ip a
setting the network namespace "ovnext" failed: Invalid argument
[root@vnode-117-35 ~]# ip netns exec ovnext ip a
setting the network namespace "ovnext" failed: Invalid argument
[root@vnode-117-35 ~]# ip netns exec ovnext ip a
setting the network namespace "ovnext" failed: Invalid argument
[root@vnode-117-35 ~]# ip netns exec ovnext bash
setting the network namespace "ovnext" failed: Invalid argument
have some problem.
Expected Behavior
The text was updated successfully, but these errors were encountered: