Activity log for bug #1995078

Date Who What changed Old value New value Message
2022-10-28 08:32:50 Michal Nasiadka bug added bug
2022-10-28 08:34:24 Bartosz Bezak bug added subscriber Bartosz Bezak
2022-11-07 07:59:08 Elvira García Ruiz neutron: status New Confirmed
2022-11-07 08:00:08 Elvira García Ruiz neutron: importance Undecided High
2022-11-07 08:09:05 Elvira García Ruiz tags ovn
2022-11-11 16:26:20 Rodolfo Alonso bug added subscriber Rodolfo Alonso
2022-11-11 17:09:16 Rodolfo Alonso bug watch added https://bugzilla.redhat.com/show_bug.cgi?id=1766930
2022-11-15 09:40:35 Bartosz Bezak bug task added kolla-ansible
2022-11-15 09:40:59 Bartosz Bezak nominated for series kolla-ansible/yoga
2022-11-15 09:40:59 Bartosz Bezak bug task added kolla-ansible/yoga
2022-11-15 09:40:59 Bartosz Bezak nominated for series kolla-ansible/wallaby
2022-11-15 09:40:59 Bartosz Bezak bug task added kolla-ansible/wallaby
2022-11-15 09:40:59 Bartosz Bezak nominated for series kolla-ansible/zed
2022-11-15 09:40:59 Bartosz Bezak bug task added kolla-ansible/zed
2022-11-15 09:40:59 Bartosz Bezak nominated for series kolla-ansible/xena
2022-11-15 09:40:59 Bartosz Bezak bug task added kolla-ansible/xena
2022-11-15 10:21:03 OpenStack Infra kolla-ansible: status New In Progress
2022-11-15 16:52:10 OpenStack Infra kolla-ansible: status In Progress Fix Released
2022-11-15 18:12:48 Michal Nasiadka neutron: status Confirmed Invalid
2022-11-15 18:13:49 OpenStack Infra kolla-ansible/yoga: status New In Progress
2022-11-15 18:13:59 OpenStack Infra kolla-ansible/xena: status New In Progress
2022-11-15 18:14:12 OpenStack Infra kolla-ansible/wallaby: status New In Progress
2022-11-16 15:55:55 OpenStack Infra kolla-ansible/yoga: status In Progress Fix Committed
2022-11-16 16:17:52 OpenStack Infra kolla-ansible/xena: status In Progress Fix Committed
2022-11-16 16:17:59 OpenStack Infra kolla-ansible/wallaby: status In Progress Fix Committed
2022-11-23 11:19:46 Michal Nasiadka neutron: status Invalid Confirmed
2022-12-09 14:49:53 OpenStack Infra kolla-ansible/xena: status Fix Committed Fix Released
2022-12-09 14:51:59 OpenStack Infra kolla-ansible/yoga: status Fix Committed Fix Released
2023-01-23 10:14:44 Michal Nasiadka bug task deleted kolla-ansible
2023-01-23 10:15:16 Michal Nasiadka kolla-ansible/wallaby: status Fix Committed Invalid
2023-01-23 10:15:22 Michal Nasiadka kolla-ansible/xena: status Fix Released Invalid
2023-01-23 10:15:26 Michal Nasiadka kolla-ansible/zed: status Fix Released Invalid
2023-01-23 10:15:30 Michal Nasiadka kolla-ansible/yoga: status Fix Released Invalid
2023-01-26 16:51:12 Rodolfo Alonso neutron: assignee Rodolfo Alonso (rodolfo-alonso-hernandez)
2023-01-27 17:38:39 OpenStack Infra neutron: status Confirmed In Progress
2023-05-30 09:22:19 Rodolfo Alonso 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 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
2023-08-31 13:35:26 OpenStack Infra kolla-ansible/wallaby: status Invalid Fix Released
2023-09-08 08:26:27 Bartosz Bezak kolla-ansible/wallaby: status Fix Released Invalid
2023-09-08 08:26:40 Bartosz Bezak bug task deleted kolla-ansible/wallaby
2023-09-08 08:26:44 Bartosz Bezak bug task deleted kolla-ansible/xena
2023-09-08 08:26:46 Bartosz Bezak bug task deleted kolla-ansible/yoga
2023-09-08 08:26:51 Bartosz Bezak bug task deleted kolla-ansible/zed
2024-02-05 18:13:58 Jay Faulkner bug task added networking-generic-switch
2024-02-05 18:14:05 Jay Faulkner networking-generic-switch: status New Triaged
2024-02-05 18:14:07 Jay Faulkner networking-generic-switch: importance Undecided High
2024-02-07 11:58:25 Rodolfo Alonso 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 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: * (OSP17): https://bugzilla.redhat.com/show_bug.cgi?id=1826364 * (OSP17): https://bugzilla.redhat.com/show_bug.cgi?id=2259161
2024-04-11 18:30:02 Sam Schmitt bug added subscriber Sam Schmitt