August 2023 - openstack-discuss - lists.openstack.org

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 25 Aug '23

25 Aug '23

Hello Neutrinos: Due to the lack of agenda [1], today's meeting is cancelled. Have a nice weekend. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[release] Release countdown for week R-5, Aug 28 - Sep 01
by Thierry Carrez 25 Aug '23

25 Aug '23

Development Focus ----------------- We are getting close to the end of the 2023.2 Bobcat cycle! Next week on August 31st is the bobcat-3 milestone, also known as feature freeze. It's time to wrap up feature work in the services and their client libraries, and defer features that won't make it to the 2024.1 Caracal cycle. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on August 31st. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2023.2 branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… August 31st is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also the deadline for submitting a first version of your cycle-highlights. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Bobcat-3 milestone (feature freeze): August 31st (R-5 week) RC1 deadline: September 14th (R-3 week) Final RC deadline: September 28th (R-1 week) Final 2023.2 Bobcat release: October 4th, 2023 -- Thierry Carrez (ttx)

1 0

[ptl][election][neutron] PTL candidacy for 2024.1
by Brian Haley 24 Aug '23

24 Aug '23

Hello Openstack Community, I am writing to submit my candidacy for the Neutron PTL position during the 2024.1 cycle. I have worked on Openstack since Diablo (2011), starting as a cloud operator doing L2 overlay development, along with agent performance and scalability on large-scale deployments. During that time I've become a core contributor (2015) and been part of the team making sure our stable branches continue to receive all the back-ports necessary to make downstream consumption easier. I currently work for Canonical in their Sustaining Engineering group, primarily addressing customer issues, with a focus on processes and tools to help us more quickly solve them. My priorities as PTL would be the following: * Always make sure the stable branches are consumable downstream. Distros and operators are, in my opinion, the lifeblood of Openstack, so we have to make sure they are top of mind when fixing bugs, and that back-ports are done in a timely manner. * Continue pursuing CI stability. During the past 6+ cycles the Neutron community has done a great job keeping its CI healthy, as well as actively updating jobs to make sure we use resources wisely and reduce re-checks. * Keep working on, or complete, ongoing specs. There are a number of larger specs that have a great deal of development in progress, I know we can get some of these completed this cycle: ** Active-active L3 Gateway with Multihoming (LP #2002687) ** Multiple back-end support for L3 routers in ML2/OVN (LP #2020823) ** Configurable Security Group rules added by default to new Security Groups (LP #1983053) ** ML2/OVN IPv6 Distributed routing (LP #1998609) * Continue reducing the bug backlog. Over the past few cycles we were able to fix and/or close about 1/3 of our backlog (~400 bugs), but it will slowly creep back up if we let it. We also have to continue looking forward by: * Keeping the Neutron stadium ecosystem alive and healthy. There are a number of diverse projects, some without a large number of resources. We must make sure those communities receive whatever help they need, whether it's making sure we address bugs affecting them, or helping keep their CIs green. * Address any SQLAlchemy 2.0 migration issues detected. We have done a great job during the last few releases with this work, let's keep that up in 2024.1. * Starting development on newly proposed specs ** OVN interconnection (LP #2027742) * Always welcoming new contributors. Thanks for your support. -Brian Haley (haleyb, haleyb.dev(a)gmail.com)

1 0

Cinder Bug Report 2023-08-23
by Jon Bernard 23 Aug '23

23 Aug '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> Medium - Cinder-Backup stuck in creating after RBD export-diff existed and turned into zombie / <defunct> <https://bugs.launchpad.net/cinder/+bug/2031897> - Status: No comments or fix proposed Undecided - Cinder allows updating default volume type <https://bugs.launchpad.net/cinder/+bug/2031653> - Status: In Progress - Extending an attached volume leaves multipath device in inconsistent state <https://bugs.launchpad.net/os-brick/+bug/2032177> - Status: In Progress Thanks -- Jon

1 0

[puppet] Proposing core team clean up
by Takashi Kajinami 23 Aug '23

23 Aug '23

Hello, I went through the current core reviewers and found out that the current list includes some people no longer working in the OpenStack community. I'd like to propose removing the following persons from the core reviewer team as we haven't seen these people making any activity in the community recently. * Pradeep Kilambi - puppet-aodh, puppet-ceilometer, puppet-gnocchi, puppet-panko * Richard Megginson - puppet-keystone * Denis Egorenko - puppet-murano * Serg Melikyan - puppet-murano * Sergey Kolekonov - puppet-neutron * David Moreau Simard - puppet-openstack-integration * Yu xingchao - all modules Also, I confirmed that Wes Hayutin is no longer working for OpenStack and he agreed to retire from the core reviewer position. Thus I'll remove him as well. I'll be open for any feedback for one week to hear any thoughts/feedback about this removal. I'd like to take this moment to thank all people for their past work. We always welcome them back if they resume their work in this project. Thank you, Takashi KAJINAMI

3 4

Cyber Resilience Act: What Now? Aug 24 at 9 AM (CST) / 14:00 UTC
by Kristin Barrientos 23 Aug '23

23 Aug '23

Hi everyone, This week’s OpenInfra Live episode is brought to you by open source community leaders. Episode: On this episode of OpenInfra Live, we will discuss the EU Cyber Resilience Act's impact on open source software. The OpenInfra Foundation and many other open source organizations have expressed concerns about the proposed text, urging the European lawmakers to take into account the specificity of open source open collaboration in the legislation. Join and engage live with our expert panelists as they discuss the current state of the proposal, its potential consequences, what we can still do about it, and what other pieces of upcoming legislation we should watch for. Date and time: Aug 24, 2023 at 9:00 AM CST (14:00 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=u6Dh0nXivqM LinkedIn: https://www.linkedin.com/events/7095407763538763776/comments/ WeChat: The recording will be posted on OpenInfra Foundation WeChat after the live stream Speakers: Thierry Carrez, Allison Randal, Mike Milinkovich, Ciarán O'Riordan Have an idea for a future episode? Share it now at ideas.openinfra.live. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

[cinder] 2023.2 (Bobcat) R-6 virtual mid cycle on 23 Aug, 2023
by Rajat Dhasmana 23 Aug '23

23 Aug '23

Hello Argonauts, As discussed in last week's cinder upstream meeting[1], we will be conducting our second mid cycle of 2023.2 Bobcat on 23rd August, 2023 (R-6 week). Following are the details: Date: 23rd August, 2023 Time: 1400-1600 UTC Meeting link: https://meet.google.com/qqs-xjzg-ccm Etherpad: https://etherpad.opendev.org/p/cinder-bobcat-midcycles We have almost a week's time so please add your topics! [1] https://meetings.opendev.org/irclogs/%23openstack-meeting-alt/%23openstack-…

1 2

[neutron][tap-as-a-service][release] Deletion old branches of taas
by Rodolfo Alonso Hernandez 23 Aug '23

23 Aug '23

Hello: I would like to revive the mail sent by Lajos about this topic: https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03127…. In a nutshell: we don't have releases from Ocata to Stein of TaaS because it was moved out from the stadium projects. However we still have issues with the zuul configs. Because we can't release an EOL patch, I would ask the release team to remove these 5 branches (Ocata, Pike, Queens, Rocky and Stein) from the git repository. If that is not possible, I'll send patches to these branches to remove the .zuul file. Regards. [1]https://zuul.opendev.org/t/openstack/config-errors

1 0

[ovn] VM in external network unable to arp
by Justin Lamp 22 Aug '23

22 Aug '23

Hey, we are using OVN 22.03 and face an issue where a VM that is directly connected to the provider network won't be accessible, because it cannot arp for the Gateway IP. OVN routers do reply to the arp request though. We know that this exact scenario works as we have it running in our staging environment. Oddly enough if the right MAC-IP Binding is manually defined within the VM and the Gateway, the traffic will begin to flow correctly according to the right SGs. I did an ovn-trace and were able to see that the traffic is supposed to be flooded to the right ports. The ovs-trace on the other hand did not show the same picture. It just did 4k recirculations and then dropped the packet. I already restarted the ovn-controller on the right hv, but that did not do anything. The LSP: $ ovn-nbctl list Logical_Switch_Port cfce175b-9d88-4c2e-a5cc-d76cd5c71deb _uuid : c5dfb248-941e-4d4e-af1a-9ccafc22db70 addresses : ["fa:16:3e:a2:d7:1a 2a02:ed80:0:3::341 91.198.2.33"<fa:16:3e:a2:d7:1a2a02:ed80:0:3::34191.198.2.33>] dhcpv4_options : 1922ee38-282f-4f5c-ade8-6cd157ee52e9 dhcpv6_options : [] dynamic_addresses : [] enabled : true external_ids : {"neutron:cidrs"<neutron:cidrs>="2a02:ed80:0:3::341/64 91.198.2.33/24", "neutron:device_id"<neutron:device_id>="8062ec61-0c68-41dd-b77c-e8b72ad16a88", "neutron:device_owner"<neutron:device_owner>="compute:AZ1"<compute:AZ1>, "neutron:network_name"<neutron:network_name>=neutron-210e26d7-942f-4e17-89b2-571eee87d7e4, "neutron:port_name"<neutron:port_name>="", "neutron:project_id"<neutron:project_id>="99fb21796a8f4cbda42ba5b9d1e307dd", "neutron:revision_number"<neutron:revision_number>="16", "neutron:security_group_ids"<neutron:security_group_ids>="3e41777f-7aa4-4368-9992-5ca7cc2a5372 873b3b62-0918-4b1e-be73-fdbed50d2ac2"} ha_chassis_group : [] name : "cfce175b-9d88-4c2e-a5cc-d76cd5c71deb" options : {mcast_flood_reports="true", requested-chassis=net-openstack-hv31} parent_name : [] port_security : ["fa:16:3e:a2:d7:1a 2a02:ed80:0:3::341 91.198.2.33"<fa:16:3e:a2:d7:1a2a02:ed80:0:3::34191.198.2.33>] tag : [] tag_request : [] type : "" up : true The PB: $ ovn-sbctl find Port_Binding logical_port=cfce175b-9d88-4c2e-a5cc-d76cd5c71deb _uuid : e9e5ce44-698f-4a29-acd1-2f24cc1d1950 chassis : c944c21a-3344-4fda-ab4e-a4cc07403125 datapath : 993b44d5-1629-4e9b-b44e-24096d8b3959 encap : [] external_ids : {"neutron:cidrs"<neutron:cidrs>="2a02:ed80:0:3::341/64 91.198.2.33/24", "neutron:device_id"<neutron:device_id>="8062ec61-0c68-41dd-b77c-e8b72ad16a88", "neutron:device_owner"<neutron:device_owner>="compute:AZ1"<compute:AZ1>, "neutron:network_name"<neutron:network_name>=neutron-210e26d7-942f-4e17-89b2-571eee87d7e4, "neutron:port_name"<neutron:port_name>="", "neutron:project_id"<neutron:project_id>="99fb21796a8f4cbda42ba5b9d1e307dd", "neutron:revision_number"<neutron:revision_number>="16", "neutron:security_group_ids"<neutron:security_group_ids>="3e41777f-7aa4-4368-9992-5ca7cc2a5372 873b3b62-0918-4b1e-be73-fdbed50d2ac2"} gateway_chassis : [] ha_chassis_group : [] logical_port : "cfce175b-9d88-4c2e-a5cc-d76cd5c71deb" mac : ["fa:16:3e:a2:d7:1a 2a02:ed80:0:3::341 91.198.2.33"<fa:16:3e:a2:d7:1a2a02:ed80:0:3::34191.198.2.33>] nat_addresses : [] options : {mcast_flood_reports="true", requested-chassis=net-openstack-hv31} parent_port : [] requested_chassis : c944c21a-3344-4fda-ab4e-a4cc07403125 tag : [] tunnel_key : 344 type : "" up : true virtual_parent : [] The LS: $ ovn-nbctl list Logical_Switch public-network _uuid : 56d8be55-462a-4b93-8710-3c79ca386213 acls : [] copp : [] dns_records : [] external_ids : {"neutron:mtu"<neutron:mtu>="1500", "neutron:network_name"<neutron:network_name>=public-network, "neutron:revision_number"<neutron:revision_number>="21"} forwarding_groups : [] load_balancer : [] load_balancer_group : [] name : neutron-210e26d7-942f-4e17-89b2-571eee87d7e4 other_config : {mcast_flood_unregistered="false", mcast_snoop="false"} ports : [00225774-8fbc-473f-ae5e-d486c54212c8, ..., c5dfb248-941e-4d4e-af1a-9ccafc22db70, ... qos_rules : [] The patchport: $ ovn-nbctl list Logical_Switch_Port provnet-aa35051c-6fc0-463a-8807-0cb28903be14 _uuid : f7259aeb-0e63-4d20-8a8e-54ebf454a524 addresses : [unknown] dhcpv4_options : [] dhcpv6_options : [] dynamic_addresses : [] enabled : [] external_ids : {} ha_chassis_group : [] name : provnet-aa35051c-6fc0-463a-8807-0cb28903be14 options : {mcast_flood="false", mcast_flood_reports="true", network_name=physnet1} parent_name : [] port_security : [] tag : [] tag_request : [] type : localnet up : false I hope I provided the needed context! Thanks in advance! Best regards, Justin Lamp -- Justin Lamp Systems Engineer NETWAYS Managed Services GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 CEO: Julian Hein, Bernd Erk, Sebastian Saemann | AG Nuernberg HRB25207 https://www.netways.de | justin.lamp(a)netways.de ** stackconf 2023 - September - https://stackconf.eu ** ** OSMC 2023 - November - https://osmc.de ** ** NETWAYS Web Services - https://nws.netways.de ** ** NETWAYS Trainings - https://netways.de/trainings **

4 5

Need assistance
by Gk Gk 22 Aug '23

22 Aug '23

Hi All, We have an openstack ansible stein version setup. We had a vm on it which we deleted. The associated neutron port was also deleted and the vm uuid is gone from the nova as well. It had a provider network ip. Even after deleting the vm, we are still finding that ssh port 22 on that IP is responding. So I logged into the hypervisor (compute node) on which that vm was there before deletion and found that the libvirtd service was is error state with the following logs in the nova-compute service: --------- 2023-08-18 10:08:51.463 12587 INFO nova.service [-] Starting compute node (version 19.3.2) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host self.force_reraise() 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host six.reraise(self.type_, self.value, self.tb) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 442, in _get_connection 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host self._wrapped_conn = self._get_new_connection() 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 396, in _get_new_connection 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host wrapped_conn = self._connect(self._uri, self._read_only) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 252, in _connect 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host libvirt.openAuth, uri, auth, flags) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/eventlet/tpool.py", line 148, in proxy_call 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host rv = execute(f, *args, **kwargs) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/eventlet/tpool.py", line 129, in execute 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host six.reraise(c, e, tb) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/eventlet/tpool.py", line 83, in tworker 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host rv = meth(*args, **kwargs) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/libvirt.py", line 104, in openAuth 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host if ret is None:raise libvirtError('virConnectOpenAuth() failed') 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service [req-4108e9e2-2afd-472e-a4d9-fcccffc380dc - - - - -] Error starting thread.: HypervisorUnavailable: Connection to the hypervisor is broken on host 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service Traceback (most recent call last): 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/oslo_service/service.py", line 810, in run_service 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service service.start() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/service.py", line 176, in start 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service self.manager.init_host() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/compute/manager.py", line 1225, in init_host 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service self.driver.init_host(host=self.host) 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 503, in init_host 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service self._do_quality_warnings() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 471, in _do_quality_warnings 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service caps = self._host.get_capabilities() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 664, in get_capabilities 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service xmlstr = self.get_connection().getCapabilities() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 482, in get_connection 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service raise exception.HypervisorUnavailable() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service HypervisorUnavailable: Connection to the hypervisor is broken on host 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service 2023-08-22 14:28:07.678 12587 INFO nova.virt.libvirt.driver [-] Connection event '0' reason 'Failed to connect to libvirt: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused' ----- However that particular neutron port for that vm is also deleted. We cant find it in the neutron db. So how is it possible for that VM IP to be responding on port 22 even after it is deleted. Please help me here. Thanks Kumar

4 3