** Changed in: ovn (Ubuntu)
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967856
Title:
Hairpin traffic does not work with centralized NAT gw
To manage
** Changed in: ovn (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967856
Title:
Hairpin traffic does not work with centralized NAT gw
To manage
** Also affects: openvswitch (Ubuntu)
Importance: Undecided
Status: New
** Changed in: openvswitch (Ubuntu)
Status: New => Triaged
** Changed in: openvswitch (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
A possible fix is being discussed in [7].
7: https://mail.openvswitch.org/pipermail/ovs-dev/2022-May/393981.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967856
Title:
Hairpin traffic does
A update on some findings.
If we either revert OVS commit [4], OR change a open vswitch kernel data
path function [5] to always return 'false' (credits to Numan), the
problem goes away.
This also appears to be a root of a different issue previously reported
to the ovs-discuss list [6].
4:
The current line of thought is that the change in OVN has uncovered a
conntrack related bug in either OVS, the OVS kernel datapath or kernel
CT in general ref [3].
3: https://mail.openvswitch.org/pipermail/ovs-dev/2022-April/393426.html
--
You received this bug notification because you are a
** Patch added: "test-synthesis.patch"
https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+attachment/5579267/+files/test-synthesis.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Updated OVN to main and it unfortunately made no difference.
The combination of stateless on the NAT rule and the allow-related ACLs
does indeed look strange, but this is how OpenStack sets it up. Have not
looked into whether that makes sense or not yet.
To ensure we're looking at the same thing
It works fine for me
-
[root@ovn-chassis-1 data]# ip netns exec vm1 ping 10.78.95.196
PING 10.78.95.196 (10.78.95.196) 56(84) bytes of data.
64 bytes from 10.78.95.196: icmp_seq=1 ttl=62 time=1.18 ms
64 bytes from 10.78.95.196: icmp_seq=2 ttl=62 time=0.651 ms
64 bytes from
Sure thing!
In this DB the active gateway chassis is `deep-ferret.maas` and the
instance on `comic-perch.maas` is unable to have two ping sessions to
itself using non-distributed FIP 10.78.95.196.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "ovnsb_db.db"
https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+attachment/5577953/+files/ovnsb_db.db
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967856
Title:
** Attachment added: "ovnnb_db.db"
https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1967856/+attachment/5577952/+files/ovnnb_db.db
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967856
Title:
Is it possible to attach the OVN dbs ?
I'm not able to reproduce it locally. For me a different zone for snat
is used on the gateway chassis for the hairpin traffic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ovn (Ubuntu)
Status: New => Triaged
** Changed in: ovn (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967856
Title:
Hairpin traffic
14 matches
Mail list logo
