Hi,
I don't know what libvirt OVN hook is though. Do you have a link?
This suggests that `requested-chassis` for the OVN port is, at least for a
moment, set to `null`, while both hosts have the interface with `iface-id`
set to the port ID. Your hook should avoid it. (Always have
requested-chassis
On Tue, Aug 6, 2024 at 6:09 AM wrote:
>
>
> On 05/08/2024 19:16, Ihar Hrachyshka wrote:
>
> Hi,
>
> I don't know what libvirt OVN hook is though. Do you have a link?
>
>
> https://docs.openvswitch.org/en/latest/howto/libvirt/
> https://www.redhat.com/sysadmin/libvirt-open-vswitch
>
>
This *seems*
On Tue, Aug 6, 2024 at 11:44 AM wrote:
>
>
> On 06/08/2024 16:22, Ihar Hrachyshka wrote:
>
> On Tue, Aug 6, 2024 at 6:09 AM wrote:
>
>>
>>
>> On 05/08/2024 19:16, Ihar Hrachyshka wrote:
>>
>> Hi,
>>
>> I don't know what libvirt OVN hook is though. Do you have a link?
>>
>>
>> https://docs.openvs
On Wed, Apr 3, 2024 at 4:15 PM Brian Haley via discuss <
ovs-discuss@openvswitch.org> wrote:
> Hi,
>
> I recently have been seeing issues in a large environment where the
> listen backlog of ovsdb-server, both NB and SB, is getting over-flowed,
> for example:
>
> 17842 times the listen queue of a
On Thu, May 29, 2025 at 11:53 AM engineer2024 via discuss <
ovs-discuss@openvswitch.org> wrote:
> Thanks for the response.
>
> This is not what I exactly asked. This scenario is specifically for the
> sriov ports. In this case, how the pkt from the physical nic go back to the
> same node ? Two qu
The flipping could explain connectivity issues for metadata. AFAIR the HA
group membership is managed by Neutron itself, so if you see the group's
`ha_chassis` list flipping, the problem is probably on the neutron side.
Anything interesting in neutron logs?
You haven't confirmed that you have othe
