[Yahoo-eng-team] [Bug 1995078] Re: OVN: HA chassis group priority is different than gateway chassis priority
** Also affects: networking-generic-switch Importance: Undecided Status: New ** Changed in: networking-generic-switch Status: New => Triaged ** Changed in: networking-generic-switch Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1995078 Title: OVN: HA chassis group priority is different than gateway chassis priority Status in Networking ML2 Generic Switch : Triaged Status in neutron: In Progress Bug description: OpenStack release affected - Wallaby, Xena and Yoga for sure OVN version: 21.12 (from CentOS NFV SIG repos) Host OS: CentOS Stream 8 Neutron creates External ports for bare metal instances and uses ha_chassis_group. Neutron normally defines a different priority for Routers LRP gateway chassis and ha_chassis_group. I have a router with two VLANs attached - external (used for internet connectivity - SNAT or DNAT/Floating IP) and internal VLAN network hosting bare metal servers (and some Geneve networks for VMs). If an External port’s HA chassis group active chassis is different than gateway chassis (external vlan network) active chassis - those bare metal servers have intermittent network connectivity for any traffic going through that router. In a thread on ovs-discuss ML - Numan Siddique wrote that "it is recommended that the same controller which is actively handling the gateway traffic also handles the external ports" More information in this thread - https://mail.openvswitch.org/pipermail/ovs- discuss/2022-October/052067.html Bugzilla reference (OSP 17): https://bugzilla.redhat.com/show_bug.cgi?id=1826364 To manage notifications about this bug go to: https://bugs.launchpad.net/networking-generic-switch/+bug/1995078/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1995078] Re: OVN: HA chassis group priority is different than gateway chassis priority
** Changed in: kolla-ansible/wallaby Status: Fix Released => Invalid ** No longer affects: kolla-ansible/wallaby ** No longer affects: kolla-ansible/xena ** No longer affects: kolla-ansible/yoga ** No longer affects: kolla-ansible/zed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1995078 Title: OVN: HA chassis group priority is different than gateway chassis priority Status in neutron: In Progress Bug description: OpenStack release affected - Wallaby, Xena and Yoga for sure OVN version: 21.12 (from CentOS NFV SIG repos) Host OS: CentOS Stream 8 Neutron creates External ports for bare metal instances and uses ha_chassis_group. Neutron normally defines a different priority for Routers LRP gateway chassis and ha_chassis_group. I have a router with two VLANs attached - external (used for internet connectivity - SNAT or DNAT/Floating IP) and internal VLAN network hosting bare metal servers (and some Geneve networks for VMs). If an External port’s HA chassis group active chassis is different than gateway chassis (external vlan network) active chassis - those bare metal servers have intermittent network connectivity for any traffic going through that router. In a thread on ovs-discuss ML - Numan Siddique wrote that "it is recommended that the same controller which is actively handling the gateway traffic also handles the external ports" More information in this thread - https://mail.openvswitch.org/pipermail/ovs- discuss/2022-October/052067.html Bugzilla reference (OSP 17): https://bugzilla.redhat.com/show_bug.cgi?id=1826364 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1995078/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1995078] Re: OVN: HA chassis group priority is different than gateway chassis priority
** No longer affects: kolla-ansible ** Changed in: kolla-ansible/wallaby Status: Fix Committed => Invalid ** Changed in: kolla-ansible/xena Status: Fix Released => Invalid ** Changed in: kolla-ansible/zed Status: Fix Released => Invalid ** Changed in: kolla-ansible/yoga Status: Fix Released => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1995078 Title: OVN: HA chassis group priority is different than gateway chassis priority Status in kolla-ansible wallaby series: Invalid Status in kolla-ansible xena series: Invalid Status in kolla-ansible yoga series: Invalid Status in kolla-ansible zed series: Invalid Status in neutron: Confirmed Bug description: OpenStack release affected - Wallaby, Xena and Yoga for sure OVN version: 21.12 (from CentOS NFV SIG repos) Host OS: CentOS Stream 8 Neutron creates External ports for bare metal instances and uses ha_chassis_group. Neutron normally defines a different priority for Routers LRP gateway chassis and ha_chassis_group. I have a router with two VLANs attached - external (used for internet connectivity - SNAT or DNAT/Floating IP) and internal VLAN network hosting bare metal servers (and some Geneve networks for VMs). If an External port’s HA chassis group active chassis is different than gateway chassis (external vlan network) active chassis - those bare metal servers have intermittent network connectivity for any traffic going through that router. In a thread on ovs-discuss ML - Numan Siddique wrote that "it is recommended that the same controller which is actively handling the gateway traffic also handles the external ports" More information in this thread - https://mail.openvswitch.org/pipermail/ovs- discuss/2022-October/052067.html To manage notifications about this bug go to: https://bugs.launchpad.net/kolla-ansible/wallaby/+bug/1995078/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1995078] Re: OVN: HA chassis group priority is different than gateway chassis priority
After doing all those changes in kolla-ansible - we found that data traffic bandwidth for External VLAN ports is kilobytes per second (around 30-100 kbytes/sec) compared to 200 megabytes/sec before. Probably that's related to MAC flooding issues in OVN. If we remove ovn-chassis-mac-mappings on network nodes - and ha_chassis_group active chassis and gateway_chassis active chassis are the same - everything works fine (except HA). Any other ideas? ** Changed in: neutron Status: Invalid => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1995078 Title: OVN: HA chassis group priority is different than gateway chassis priority Status in kolla-ansible: Fix Released Status in kolla-ansible wallaby series: Fix Committed Status in kolla-ansible xena series: Fix Committed Status in kolla-ansible yoga series: Fix Committed Status in kolla-ansible zed series: Fix Released Status in neutron: Confirmed Bug description: OpenStack release affected - Wallaby, Xena and Yoga for sure OVN version: 21.12 (from CentOS NFV SIG repos) Host OS: CentOS Stream 8 Neutron creates External ports for bare metal instances and uses ha_chassis_group. Neutron normally defines a different priority for Routers LRP gateway chassis and ha_chassis_group. I have a router with two VLANs attached - external (used for internet connectivity - SNAT or DNAT/Floating IP) and internal VLAN network hosting bare metal servers (and some Geneve networks for VMs). If an External port’s HA chassis group active chassis is different than gateway chassis (external vlan network) active chassis - those bare metal servers have intermittent network connectivity for any traffic going through that router. In a thread on ovs-discuss ML - Numan Siddique wrote that "it is recommended that the same controller which is actively handling the gateway traffic also handles the external ports" More information in this thread - https://mail.openvswitch.org/pipermail/ovs- discuss/2022-October/052067.html To manage notifications about this bug go to: https://bugs.launchpad.net/kolla-ansible/+bug/1995078/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1995078] Re: OVN: HA chassis group priority is different than gateway chassis priority
Hi Rodolfo, At the moment it seems that it has fixed the issue. Basically we added that in the past not thinking about external ports. I marked it as invalid in Neutron, if we'll see any issues - we'll reopen in future. Thanks for your help! ** Changed in: neutron Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1995078 Title: OVN: HA chassis group priority is different than gateway chassis priority Status in kolla-ansible: Fix Released Status in kolla-ansible wallaby series: In Progress Status in kolla-ansible xena series: In Progress Status in kolla-ansible yoga series: In Progress Status in kolla-ansible zed series: Fix Released Status in neutron: Invalid Bug description: OpenStack release affected - Wallaby, Xena and Yoga for sure OVN version: 21.12 (from CentOS NFV SIG repos) Host OS: CentOS Stream 8 Neutron creates External ports for bare metal instances and uses ha_chassis_group. Neutron normally defines a different priority for Routers LRP gateway chassis and ha_chassis_group. I have a router with two VLANs attached - external (used for internet connectivity - SNAT or DNAT/Floating IP) and internal VLAN network hosting bare metal servers (and some Geneve networks for VMs). If an External port’s HA chassis group active chassis is different than gateway chassis (external vlan network) active chassis - those bare metal servers have intermittent network connectivity for any traffic going through that router. In a thread on ovs-discuss ML - Numan Siddique wrote that "it is recommended that the same controller which is actively handling the gateway traffic also handles the external ports" More information in this thread - https://mail.openvswitch.org/pipermail/ovs- discuss/2022-October/052067.html To manage notifications about this bug go to: https://bugs.launchpad.net/kolla-ansible/+bug/1995078/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1995078] Re: OVN: HA chassis group priority is different than gateway chassis priority
Reviewed: https://review.opendev.org/c/openstack/kolla-ansible/+/864510 Committed: https://opendev.org/openstack/kolla-ansible/commit/8bf8656dbad3def707eca2d8ddd2c9bfed389b86 Submitter: "Zuul (22348)" Branch:master commit 8bf8656dbad3def707eca2d8ddd2c9bfed389b86 Author: Bartosz Bezak Date: Tue Nov 15 11:08:15 2022 +0100 Generate ovn-chassis-mac-mappings on ovn-controller group Previously ovn-chassis-mac-mappings [1] has been added only to ovn-controller-compute group. However external ports are being scheduled on network nodes, therefore we need also do that there. Closes-Bug: 1995078 [1] https://github.com/ovn-org/ovn/blob/v22.09.0/controller/ovn-controller.8.xml#L239 Change-Id: Ie62e9220bad56262cad602ca1480e6ca65827819 ** Changed in: kolla-ansible Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1995078 Title: OVN: HA chassis group priority is different than gateway chassis priority Status in kolla-ansible: Fix Released Status in kolla-ansible wallaby series: New Status in kolla-ansible xena series: New Status in kolla-ansible yoga series: New Status in kolla-ansible zed series: Fix Released Status in neutron: Confirmed Bug description: OpenStack release affected - Wallaby, Xena and Yoga for sure OVN version: 21.12 (from CentOS NFV SIG repos) Host OS: CentOS Stream 8 Neutron creates External ports for bare metal instances and uses ha_chassis_group. Neutron normally defines a different priority for Routers LRP gateway chassis and ha_chassis_group. I have a router with two VLANs attached - external (used for internet connectivity - SNAT or DNAT/Floating IP) and internal VLAN network hosting bare metal servers (and some Geneve networks for VMs). If an External port’s HA chassis group active chassis is different than gateway chassis (external vlan network) active chassis - those bare metal servers have intermittent network connectivity for any traffic going through that router. In a thread on ovs-discuss ML - Numan Siddique wrote that "it is recommended that the same controller which is actively handling the gateway traffic also handles the external ports" More information in this thread - https://mail.openvswitch.org/pipermail/ovs- discuss/2022-October/052067.html To manage notifications about this bug go to: https://bugs.launchpad.net/kolla-ansible/+bug/1995078/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1995078] Re: OVN: HA chassis group priority is different than gateway chassis priority
** Also affects: kolla-ansible Importance: Undecided Status: New ** Also affects: kolla-ansible/yoga Importance: Undecided Status: New ** Also affects: kolla-ansible/wallaby Importance: Undecided Status: New ** Also affects: kolla-ansible/zed Importance: Undecided Status: New ** Also affects: kolla-ansible/xena Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1995078 Title: OVN: HA chassis group priority is different than gateway chassis priority Status in kolla-ansible: New Status in kolla-ansible wallaby series: New Status in kolla-ansible xena series: New Status in kolla-ansible yoga series: New Status in kolla-ansible zed series: New Status in neutron: Confirmed Bug description: OpenStack release affected - Wallaby, Xena and Yoga for sure OVN version: 21.12 (from CentOS NFV SIG repos) Host OS: CentOS Stream 8 Neutron creates External ports for bare metal instances and uses ha_chassis_group. Neutron normally defines a different priority for Routers LRP gateway chassis and ha_chassis_group. I have a router with two VLANs attached - external (used for internet connectivity - SNAT or DNAT/Floating IP) and internal VLAN network hosting bare metal servers (and some Geneve networks for VMs). If an External port’s HA chassis group active chassis is different than gateway chassis (external vlan network) active chassis - those bare metal servers have intermittent network connectivity for any traffic going through that router. In a thread on ovs-discuss ML - Numan Siddique wrote that "it is recommended that the same controller which is actively handling the gateway traffic also handles the external ports" More information in this thread - https://mail.openvswitch.org/pipermail/ovs- discuss/2022-October/052067.html To manage notifications about this bug go to: https://bugs.launchpad.net/kolla-ansible/+bug/1995078/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
