June 2023 - openstack-discuss - lists.openstack.org

[neutron] Transition networking-odl Ussuri to EOL
by Rodolfo Alonso Hernandez 28 Jun '23

28 Jun '23

Hello Neutrinos: Yesterday we found that we are still executing some periodic jobs for networking-odl in some stable releases. For the newer branches, we have proposed the corresponding patches to remove these zuul jobs [1][2]. The problem is in the Ussuri branch [3], which is completely broken (UTs, pep8, etc). This is why I'm proposing to transition it to EOL. If you have any concerns, suggestions or questions, please let me know (via mail or IRC in the #openstack-neutron channel). Regards. [1]https://review.opendev.org/c/openstack/networking-odl/+/887080 [2]https://review.opendev.org/c/openstack/networking-odl/+/887077 [3]https://review.opendev.org/c/openstack/networking-odl/+/887076

1 0

[largescale-sig] Next meeting: June 28, 8utc
by Thierry Carrez 28 Jun '23

28 Jun '23

Hi everyone, The Large Scale SIG will be meeting for the last time before the Northern hemisphere summer this Wednesday in #openstack-operators on OFTC IRC, at 8UTC, our APAC+EU-friendly time. I will be chairing. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230628T08 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[Neutron Community] Neutron OVN vs OVS
by Karl Kloppenborg 27 Jun '23

27 Jun '23

Hi Neutron community, Firstly, apologies if this has been asked before, a cursory search of the list rendered no information. At a high level, is OVN replacing OVS in terms of the preferred standard neutron deployment? I am seeing more and more about OVN on the mailing list and wondering if I should be investigating it to supersede OVS standalone. Again, apologies if this is vague/asked before. Kind Regards, Karl Kloppenborg. Openstack-Helm Team.

2 2

[kolla] Transitioning stable/wallaby to EOL
by Michał Nasiadka 27 Jun '23

27 Jun '23

Hello Koalas, On a weekly meeting last week - we’ve decided that due to core team size we’re unable to support that many stable branches - and with the recent release of Antelope (2023.1) we are going to transition Wallaby branch to End of Life. That means the branch will get removed and wallaby-eol tag will be available for those that are still using that code for their deployments. Best regards, Michal

1 0

[tc] July 4 TC Meeting cancelled; next meeting July 11
by Jay Faulkner 27 Jun '23

27 Jun '23

Hi all, The next Technical Committee meeting, as currently scheduled, would fall on July 4th, a US holiday. For this reason, we've cancelled the July 4th meeting. The next scheduled meeting of the TC will be July 11th. As always, if you need anything from us in the meantime, we're in #openstack-tc. Thanks, Jay Faulkner Technical Committee Vice-Chair

1 0

[qa] Cancelling office hour July 4th
by Martin Kopec 27 Jun '23

27 Jun '23

Hello everyone, I'll be on PTO starting this Thursday (June 29th) until July 10th. Therefore I'm gonna cancel our next office hour on July 4th. In case of emergencies, contact me via email - I'll be off the IRC. Thanks, -- Martin Kopec Principal Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0

Cloudkitty support for Opensearch on Yoga
by wodel youchi 27 Jun '23

27 Jun '23

Hi, Reading the The release notes about Cloudkitty I read this : "Support for using Elasticsearch as a storage backend is being deprecated in the Antelope release in favour of OpenSearch. We will try to keep CloudKitty compatible with both solutions. However, we will only test with OpenSearch." What is the state of the support of Opensearch on Cloudkitty? If it is fully supported, does Openstack Yoga offer the same support? Regards.

2 1

[neutron] Bug deputy report - week of Jun 19th
by Slawek Kaplonski 27 Jun '23

27 Jun '23

Hi, I was bug deputy last week and here is summary of new bugs opened in Neutron: ## Critical ## * https://bugs.launchpad.net/neutron/+bug/2024903 - [neutron-lib] FT "test_negative_update_floatingip_port_forwarding" failing randomly very often - already fixed by Rodolfo, * https://bugs.launchpad.net/neutron/+bug/2025126 - Functional MySQL sync test failing with oslo/sqlalchemy master branch - not assigned ## High ## * https://bugs.launchpad.net/neutron/+bug/2024674 - Unit tests fails with oslo_db.exception.DBNonExistentTable: (sqlite3.OperationalError) no such table: ml2_geneve_allocations when run with low concurrency or on loaded systems - assigned to Yatin * https://bugs.launchpad.net/neutron/+bug/2025129 - DvrLocalRouter init references namespace before it is created - not assigned ## Medium ## * https://bugs.launchpad.net/neutron/+bug/2024381 - keepalived fails to start after updating DVR-HA internal network MTU - assigned to Anton Kurbatov, fix proposed, * https://bugs.launchpad.net/neutron/+bug/2024912 - [ovn-octavia-provider] Updating status on incorrect pool when HM delete - assigned to Fernando * https://bugs.launchpad.net/neutron/+bug/2025056 - Router ports without IP addresses shouldn't be allowed to deletion using port's API directly - assigned to slaweq, fix proposed ## Whishlist ## * https://bugs.launchpad.net/neutron/+bug/2024502 - Tempest: add scenario to validate that stateless SG rules are working in presence of Load Balancer attached to the same network - assigned to slaweq, * https://bugs.launchpad.net/neutron/+bug/2024621 - tempest: add scenario for reverse DNS resolution - not assigned - I marked it as low-hanging-fruit task as I think that writing such test case is good way to start contribution to Neutron, ## RFEs ## * https://bugs.launchpad.net/neutron/+bug/2024581 - [RFE] Caching instance id in the metadata agent to have less RPC messages sent to server - not assigned * https://bugs.launchpad.net/neutron/+bug/2024921- [RFE] Formalize use of subnet service-type for draining subnets - not assigned * https://bugs.launchpad.net/neutron/+bug/2025055 - [rfe][ml2] Add a new API that supports cloning a specified security group - not assigned ## Needs triage ## * https://bugs.launchpad.net/ubuntu/+source/neutron-dynamic-routing/+bug/2024… - Address on SNAT port won't be advertised by BGP speaker - not assigned * https://bugs.launchpad.net/neutron/+bug/2024481- [ndr] neutron-bgp-dragent is racy when a service restart is made just before a speaker is added - frickler is already taking care of this one but it needs more triaging still ## Incomplete ## * https://bugs.launchpad.net/neutron/+bug/2024976 - iptable rules restoring error in l3-agent and openvswitch-agent - already taken care by Brian, it seems like it's deployment issue, -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[nova] Last Spec review day next Tuesday !
by Sylvain Bauza 27 Jun '23

27 Jun '23

Hey folks, As a reminder [1], we will have a spec review day next Tuesday June 27th. Sharpen your pens and your Gerrit patches because it will be the last spec review day for this cycle and the Spec Approval Freeze will be on July 6th [2] ! Make sure you have everything uploaded so we can look at them during this day ! After July 6th, no new features will be accepted if they need a specific spec. -Sylvain [1] https://releases.openstack.org/bobcat/schedule.html#b-nova-spec-review-day [2] https://releases.openstack.org/bobcat/schedule.html#b-nova-spec-freeze

1 1

Neutron BGP agent advertisement and l3/openvswitch-agent problems (zed)
by Bryan Huang 26 Jun '23

26 Jun '23

Dear folks, Recently, we met some neutron networking problems in our envrionment, openstack version is zed, and kolla-ansible as the deployment tool. 1. Neutron BGP agent doesn't advertise the floating IPs to the BGP peer, in case of the floating IPs were served for port forwarding, but the floating IPs attached to VM/Container were advertised correctly. so the question is this scenario supported by BGP agent, if not when will it be supported, is it in the plan? 2. iptable rules restoring error in l3-agent and openvswitch-agent (A bug was reported in launchpad: https://bugs.launchpad.net/neutron/+bug/2024976) Bug #2024976 “iptable rules restoring error in l3-agent and open...” : Bugs : neutron<https://bugs.launchpad.net/neutron/+bug/2024976> Openstack version: zed/stable OS version: Ubuntu 22.04.2 LTS Kernel version: 5.15.0-75-generic #82-Ubuntu Deployment: kolla-ansible iptable rules restoring error in l3-agent and openvswitch-agent: openvswitch-agnet log: 2023-06-23 15:54:58.616 7 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [None req-4440bce1-8c07-4243-ac1b-2566b406a30a - - - - - -] Error while processing VIF ports: neutron_lib.exceptions.ProcessExecutionError: Exit code: 2; Cmd: [... bugs.launchpad.net openvswitch-agnet log: 2023-06-23 15:54:58.616 7 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [None req-4440bce1-8c07-4243-ac1b-2566b406a30a - - - - - -] Error while processing VIF ports: neutron_lib.exceptions.ProcessExecutionError: Exit code: 2; Cmd: ['iptables-restore', '-n']; Stdin: # Generated by iptables_manager *filter :FORWARD - [0:0] :INPUT - [0:0] :OUTPUT - [0:0] :neutron-filter-top - [0:0] :neutron-openvswi-FORWARD - [0:0] :neutron-openvswi-INPUT - [0:0] :neutron-openvswi-OUTPUT - [0:0] :neutron-openvswi-local - [0:0] :neutron-openvswi-sg-chain - [0:0] :neutron-openvswi-sg-fallback - [0:0] -I FORWARD 1 -j neutron-filter-top -I FORWARD 2 -j neutron-openvswi-FORWARD -I INPUT 1 -j neutron-openvswi-INPUT -I OUTPUT 1 -j neutron-filter-top -I OUTPUT 2 -j neutron-openvswi-OUTPUT -I neutron-filter-top 1 -j neutron-openvswi-local -I neutron-openvswi-FORWARD 1 -m physdev --physdev-out tap2fcacaf9-9d --physdev-is-bridged -m comment --comment "Accept all packets when port is trusted." -j ACCEPT -I neutron-openvswi-FORWARD 2 -m physdev --physdev-in tap2fcacaf9-9d --physdev-is-bridged -m comment --comment "Accept all packets when port is trusted." -j ACCEPT -I neutron-openvswi-FORWARD 3 -m physdev --physdev-out tap8c64cce3-ea --physdev-is-bridged -m comment --comment "Accept all packets when port is trusted." -j ACCEPT -I neutron-openvswi-FORWARD 4 -m physdev --physdev-in tap8c64cce3-ea --physdev-is-bridged -m comment --comment "Accept all packets when port is trusted." -j ACCEPT -I neutron-openvswi-sg-chain 1 -j ACCEPT -I neutron-openvswi-sg-fallback 1 -m comment --comment "Default drop rule for unmatched traffic." -j DROP COMMIT # Completed by iptables_manager # Generated by iptables_manager *raw :OUTPUT - [0:0] :PREROUTING - [0:0] :neutron-openvswi-OUTPUT - [0:0] :neutron-openvswi-PREROUTING - [0:0] -I OUTPUT 1 -j neutron-openvswi-OUTPUT -I PREROUTING 1 -j neutron-openvswi-PREROUTING COMMIT # Completed by iptables_manager ; Stdout: ; Stderr: iptables-restore v1.8.7 (nf_tables): Couldn't load match `physdev':No such file or directory Error occurred at line: 19 Try `iptables-restore -h' or 'iptables-restore --help' for more information. l3-agent log: 2023-06-23 16:15:49.545 33 ERROR neutron.agent.linux.iptables_manager [-] Failure applying iptables rules: neutron_lib.exceptions.ProcessExecutionError: Exit code: 2; Cmd: ['ip', 'netns', 'exec', 'qrouter-0f0e60d0-bf51-4361-901b-4b998201b44b', 'iptables-restore', '-n']; Stdin: # Generated by iptables_manager *filter :FORWARD - [0:0] :INPUT - [0:0] :OUTPUT - [0:0] :neutron-filter-top - [0:0] :neutron-l3-agent-FORWARD - [0:0] :neutron-l3-agent-INPUT - [0:0] :neutron-l3-agent-OUTPUT - [0:0] :neutron-l3-agent-local - [0:0] :neutron-l3-agent-scope - [0:0] -I FORWARD 1 -j neutron-filter-top -I FORWARD 2 -j neutron-l3-agent-FORWARD -I INPUT 1 -j neutron-l3-agent-INPUT -I OUTPUT 1 -j neutron-filter-top -I OUTPUT 2 -j neutron-l3-agent-OUTPUT -I neutron-filter-top 1 -j neutron-l3-agent-local -I neutron-l3-agent-FORWARD 1 -j neutron-l3-agent-scope -I neutron-l3-agent-scope 1 -m mark --mark 0x1/0xffff -j DROP COMMIT # Completed by iptables_manager # Generated by iptables_manager *mangle :FORWARD - [0:0] :INPUT - [0:0] :OUTPUT - [0:0] :POSTROUTING - [0:0] :PREROUTING - [0:0] :neutron-l3-agent-FORWARD - [0:0] :neutron-l3-agent-INPUT - [0:0] :neutron-l3-agent-OUTPUT - [0:0] :neutron-l3-agent-POSTROUTING - [0:0] :neutron-l3-agent-PREROUTING - [0:0] :neutron-l3-agent-float-snat - [0:0] :neutron-l3-agent-floatingip - [0:0] :neutron-l3-agent-mark - [0:0] :neutron-l3-agent-scope - [0:0] -I FORWARD 1 -j neutron-l3-agent-FORWARD -I INPUT 1 -j neutron-l3-agent-INPUT -I OUTPUT 1 -j neutron-l3-agent-OUTPUT -I POSTROUTING 1 -j neutron-l3-agent-POSTROUTING -I PREROUTING 1 -j neutron-l3-agent-PREROUTING -I neutron-l3-agent-PREROUTING 1 -j neutron-l3-agent-mark -I neutron-l3-agent-PREROUTING 2 -j neutron-l3-agent-scope -I neutron-l3-agent-PREROUTING 3 -m connmark ! --mark 0x0/0xffff0000 -j CONNMARK --restore-mark --nfmask 0xffff0000 --ctmask 0xffff0000 -I neutron-l3-agent-PREROUTING 4 -j neutron-l3-agent-floatingip -I neutron-l3-agent-PREROUTING 5 -d 169.254.169.254/32 -i qr-+ -p tcp -m tcp --dport 80 -j MARK --set-xmark 0x1/0xffff -I neutron-l3-agent-float-snat 1 -m connmark --mark 0x0/0xffff0000 -j CONNMARK --save-mark --nfmask 0xffff0000 --ctmask 0xffff0000 COMMIT # Completed by iptables_manager # Generated by iptables_manager *nat :OUTPUT - [0:0] :POSTROUTING - [0:0] :PREROUTING - [0:0] :neutron-l3-agent-OUTPUT - [0:0] :neutron-l3-agent-POSTROUTING - [0:0] :neutron-l3-agent-PREROUTING - [0:0] :neutron-l3-agent-float-snat - [0:0] :neutron-l3-agent-snat - [0:0] :neutron-postrouting-bottom - [0:0] -I OUTPUT 1 -j neutron-l3-agent-OUTPUT -I POSTROUTING 1 -j neutron-l3-agent-POSTROUTING -I POSTROUTING 2 -j neutron-postrouting-bottom -I PREROUTING 1 -j neutron-l3-agent-PREROUTING -I neutron-l3-agent-POSTROUTING 1 ! -o rfp-0f0e60d0-b -m conntrack ! --ctstate DNAT -j ACCEPT -I neutron-l3-agent-PREROUTING 1 -d 137.175.31.207/32 -i rfp-0f0e60d0-b -j DNAT --to-destination 10.10.0.246 -I neutron-l3-agent-float-snat 1 -s 10.10.0.246/32 -j SNAT --to-source 137.175.31.207 --random-fully -I neutron-l3-agent-snat 1 -j neutron-l3-agent-float-snat -I neutron-postrouting-bottom 1 -m comment --comment "Perform source NAT on outgoing traffic." -j neutron-l3-agent-snat COMMIT # Completed by iptables_manager # Generated by iptables_manager *raw :OUTPUT - [0:0] :PREROUTING - [0:0] :neutron-l3-agent-OUTPUT - [0:0] :neutron-l3-agent-PREROUTING - [0:0] -I OUTPUT 1 -j neutron-l3-agent-OUTPUT -I PREROUTING 1 -j neutron-l3-agent-PREROUTING COMMIT # Completed by iptables_manager ; Stdout: ; Stderr: iptables-restore v1.8.7 (nf_tables): Couldn't load match `mark':No such file or directory Error occurred at line: 19 And we check the system the x_tables kernel module were loaded: # lsmod | grep x_tables x_tables 53248 12 xt_conntrack,nft_compat,xt_tcpudp,xt_physdev,xt_nat,xt_comment,ip6_tables,xt_connmark,xt_CT,ip_tables,xt_REDIRECT,xt_mark (neutron-l3-agent)[neutron@compute06 usr]$ find . -name "*mark.so" ./lib/x86_64-linux-gnu/xtables/libxt_connmark.so ./lib/x86_64-linux-gnu/xtables/libxt_mark.so ./lib/x86_64-linux-gnu/xtables/libebt_mark.so (neutron-l3-agent)[neutron@compute06 usr]$ find . -name "*physdev.so" ./lib/x86_64-linux-gnu/xtables/libxt_physdev.so Does someone have ever met the problems what is the solution the resovle them. Thanks in advance Sincerely， Bryan

2 1