CC: ovs-discuss for visibility.
It seems like this change will affect ovn-fake-multinode project
and ovn-heater as they are cloning 'master' branch by default.
Also the OVN project itself is cloning OVS master branch in one
of the CI workflows.
On 3/21/24 11:09, Simon Horman wrote:
> Recently OV
On 3/21/24 13:32, Ilya Maximets wrote:
> CC: ovs-discuss for visibility.
>
Thanks for the heads up, Ilya!
> It seems like this change will affect ovn-fake-multinode project
> and ovn-heater as they are cloning 'master' branch by default.
I opened draft PRs for ovn-fake-multinode and ovn-heater:
On 3/21/24 08:48, Qiang Qiang45 Zhang via discuss wrote:
> Problem:
>
> When the Geneve tunnel is the Bond port, TCP traffic between virtual machines
> is not connected, and PING is allowed; When the Geneve tunnel is a single
> physical port, both TCP and PING are normal.
>
> Version:
>
> ovs-vs
Hi team,
Recently, we face a weird issue on DNS resolv using OVN.
Case describe:
1. There is a VM instance or a VM cluster(3 VMs)on our deployment for a
long time, and we enable the DNS via neutron-ovn.
2. The DNS resolve works as expected in our internal network for a while.
3. Suddentlly, the D
