Public bug reported:
* Explain the bug(s)
When using ovs internal port with tc the redirect rules to internal port is back
to ingress instead of egress.
When we reinsert the skb we start from chain 0 but it could be ct state already
set so matching rules on the internal port queue would miss.
* brief explanation of fixes
When reinserting skb back to ingress queue to restart tc classification
then also reset ct.
* How to test
The setup was created by using ovn and testing iperf traffic from host
container to VF pod.
The result was ip set on the ovs bridge netdev (internal port)
The rules were from rep to eventually the internal port and internal port to
rep.
The rules were with ct actions and chains tc-policy was set to skip-hw.
Without the commit the traffic doesn’t work when hw-offload was true (offload
to tc sw only) but
does work with hw-offload false (ovs dp).
* What it could break.
Traffic not working in some cases using internal ports and CT.
** Affects: linux-bluefield (Ubuntu)
Importance: Undecided
Assignee: Bodong Wang (bodong-wang)
Status: In Progress
** Changed in: linux-bluefield (Ubuntu)
Assignee: (unassigned) => Bodong Wang (bodong-wang)
** Changed in: linux-bluefield (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935584
Title:
Fix host to pod traffic with ovn cluster using ovs internal port and
tc offload
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1935584/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
