- openstack-discuss - lists.openstack.org

Nova Multi-Cell Live Migration Issues
by Tyler Wilson 20 Feb '26

20 Feb '26

Hello All, I'm trying to get a 2 cell setup going as a test environment and am running into some troubles. I seem to be able to start VM's just fine, however when I try live-migrations I am getting this error: 2026-02-19 20:11:01.448 1 ERROR nova.conductor.manager [None req-91d4c1c6-a69f-41d4-a3ca-c0890bde0af8 - - - - - -] Migration of instance 73123ed9-d112-4030-945c-96c75a016d55 to host compute1 unexpectedly failed.: oslo_messaging.rpc.client.RemoteError: Remote error: RemoteError Remote error: CantStartEngineError No sql_connection parameter is established I see this on the following service logs nova-conductor (superconductor role only) nova-api nova-compute What is odd is that I don't see any activity in the cell-conductor when this happens, even with debug enabled. Here are the configured connection strings I have in each conductor/api/compute services: https://pastebin.com/raw/uuamtzsk Are these the correct database connection strings for each service? I'm basing this off the multi-cell diagram in the docs. The fact that the cell-conductors aren't showing any activity when this happens is throwing me off. I feel like I'm missing something here but I can't put my finger on it. Any help would be appreciated, thanks!

2 2

[release] Release countdown for week R-5, Feb 23 - 27
by Elõd Illés 20 Feb '26

20 Feb '26

Development Focus ----------------- We are getting close to the end of the 2026.1 Gazpacho cycle! Next week on February 26th, 2026 is the Gazpacho-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 2026.2 Hibiscus cycle. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on February 26th, 2026. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2026.1 branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… February 26th, 2026 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 a good time 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 -------------------------- Gazpacho-3 milestone (feature freeze): February 26th, 2026 (R-5 week) RC1 deadline: March 12th, 2026 (R-3 week) Final RC deadline: March 26th, 2026 (R-1 week) Final 2026.1 "Gazpacho" release: April 1st, 2026 2026.2 "Hibiscus" (virtual) PTG: April 20-24, 2026 Előd Illés irc: elodilles @ #openstack-release

1 0

Feb 19 Digital Sovereignty WG Recording + Next Steps
by Kendall Nelson 19 Feb '26

19 Feb '26

Hello All! Thank you to all those that were able to find the time to attend and participate in this week's meeting! For those that were not able to attend, here is the recording of today's meeting so that you can catch up and stay engaged with these efforts: https://zoom.us/rec/share/a5cXdx6RsWRNuGt8uqyQEgrVDNnIbexDag8NaUEzhcuyiUmTh… *Now, as far as next steps go: * - Soon, Allison and I will send around some samples of stance text for the landing page and we will *NEED* your feedback and opinions to make sure we have everything covered. - If you have a use case that you think would be good to share, please start working on those case studies ASAP! While we don't need them to launch the landing page (which is scheduled for March 20th-ish) the more content we have ready to go early on, the better! - If you are interested in helping with either of the other initial deliverables ( the comparison sheet or the best practices doc), please add your name to those sections of the etherpad <https://etherpad.opendev.org/p/Digital-Sovereignty-WG>. Also, if you have additional resources that would be helpful in crafting either deliverable, add them to the etherpad. Feel free to also get started throwing content in either as well! They will be living documents in draft form for a while, so nothing has to be perfect. Focus on just getting content in and we will polish things up later. When Allison and I send drafts of stances for review, we will also send out the poll for selecting the next meeting time which is slated for the week of March 9th, likely the 10th, 11th or 12th. Whew, that was a lot of information, but we have a lot of work to get done as a group! I am so excited to see this effort through with you all; we are a strong community and we are stronger together, so thank you for sharing your expertise and time with the Digital Sovereignty Working Group. -- Kendall Nelson *Senior Upstream Developer Advocate* The OpenInfra Foundation <https://openinfra.dev/>

1 0

[all] POST_FAILURE in openstack-tox-py310
by Takashi Kajinami 19 Feb '26

19 Feb '26

I feel like this week is one of the most exciting week we have had recently :-P We started seeing consistent POST_FAILURE in openstack-tox-py310 (and other jobs using py310). https://github.com/testing-cabal/testtools/issues/569 The issue was caused by testtools and was fixed in testools 2.8.4, but we likely need to rebuild the image used in CI to pull the fixed version. Please avoid mass recheck or merging any new changes now before you check the CI status carefully. Thank you, Takashi -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

2 3

[neutron] Drivers meeting canceled Friday, February 20th
by Brian Haley 19 Feb '26

19 Feb '26

Hello Neutrinos: I am going to cancel tomorrow's Drivers meeting as there are no topics on the agenda. Just a reminder that our open spec list is at [0]. Have a nice weekend! -Brian [0] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

[kolla-ansible][ironic] Simple setup for baremetal in Flamingo OpenStack
by vincent lee 19 Feb '26

19 Feb '26

Hi all, I am currently experiencing issues while setting up a basic ironic deployment. My environment consists of a controller running Ubuntu 24.04 and a baremetal host with IPMI support but no operating system installed. I am using kolla-ansible for the Flamingo version OpenStack deployment, and all configuration is being managed through the globals.yml file. One of the controller’s network interfaces is configured to provide DHCP and is connected to a physical switch. I have attached an image (Figure 1) illustrating the physical layout of my setup. My controller had the following configuration: { Two interface (eth0 and eth1) eth0: 10.42.0.1 with netmask 24 eth1: No IP assignment } My compute had the following configuration: { 5 interfaces (eth0, eth1, eth2, eth3, IPMI) eth1: No IP assignment and is connected to switch (MAC: 6F:F1:34:E9:01:29) IPMI: 10.42.0.100 connected to switch } In my globals.yml file, I have the following configuration: { openstack_release: "2025.2" # Flamingo kolla_internal_vip_address: "10.42.0.1" docker_configure_for_zun: true containerd_configure_for_zun: true containerd_grpc_gid: 42463 enable_openstack_core: true enable_haproxy: false enable_cinder: false enable_etcd: true enable_fluentd: true enable_ironic: true enable_kuryr: true enable_magnum: true enable_zun: true ironic_dnsmasq_dhcp_ranges: - range: "10.42.0.5,10.42.0.200" ironic_dnsmasq_boot_file: "pxelinux.0" ironic_cleaning_network: "public1" ironic_dnsmasq_default_gateway: "10.42.0.1" ironic_inspector_kernel_cmdline_extras: ['ipa-lldp-timeout=90.0', 'ipa-collect-lldp=1'] } After completing the deployment, I verified that all the required services are running as docker containers. Immediately afterward, I executed the necessary command to generate the admin credentials, which allows me to use the OpenStack client. 1. $pip install python-openstackclient -c https://releases.openstack.org/constraints/upper/master 2. $kolla-ansible post-deploy 3. $/path/to/venv/share/kolla-ansible/init-runonce After running the command, the following baseline was created. 1. Two network (public1 and demo-net), where public is a flat network 2. cirros image file 3. flavors After that, I uploaded a working kernel, initramfs, and ISO image to OpenStack. I verified that these images were functioning correctly by successfully launching an instance. Next, during the node enrollment process, I ran the following command to enroll my baremetal node. 1. $openstack flavor create --ram 32768 --vcpu 16 --disk 120 baremetal 2. $openstack flavor set --property resources:CUSTOM_IRONIC=1 baremetal 3. $openstack flavor set --property resources:VCPU=0 baremetal 4. $openstack flavor set --property resources:MEMORY_MB=0 baremetal 5. $openstack flavor set --property resources:DISK_GB=0 baremetal 6. $openstack baremetal node create --driver ipmi --deploy-interface direct --driver-info ipmi_username=<IPMI_usernmae> --driver-info ipmi_password=<IPMI_password> --driver-info ipmi_address=10.42.0.100 --driver-info deploy_kernel=<kernel uploaded> --driver-info deploy_ramdisk=<initramfs uploaded> --property local_gb=20 --resource-class baremetal --name My_node After enrolling the node as described above, and since I do not have an ironic Inspector setup, I manually created a port for the enrolled node using the MAC address 6F:F1:34:E9:01:29, which corresponds to the LAN interface. At this point, I am unsure how to proceed with booting the desired image onto the bare-metal host. I would greatly appreciate any guidance on the next steps required to deploy the image to the machine. Best, Vincent

1 0

[nova][meeting] Reserving time for bug scrubbing
by René Ribaud 19 Feb '26

19 Feb '26

Hi everyone, First of all, apologies for the lack of regular updates over the past few months. I haven’t managed to find the time and energy recently, but I’m trying to get back to a more regular rhythm. For the next meeting, I’d like us to explicitly reserve 10 to 15 minutes for bug scrubbing and avoid skipping it. To make this possible, I’ll adjust the agenda accordingly so that this time is clearly allocated. For those volunteering for bug scrubbing: if you have questions about specific bugs, please try to prepare them in advance and, if possible, add them to the agenda document under the Bug Scrubbing section. This should help us make that time more efficient and focused upfront. Thanks everyone, and see you at the meeting. Cheers, René

1 0

[all][elections][tc] TC Election Campaigning Kickoff
by Ian Y. Choi 18 Feb '26

18 Feb '26

Developers, The TC Election Campaigning Period has now started[1]. During the next couple days, you are all encouraged to ask the candidates questions about their platforms[2], opinions on OpenStack, community governance, and anything else that will help you to better determine how you will vote. This is the time to raise any issues you wish the future TC to consider, and to evaluate the opinions of the nominees prior to their election. Candidates, Each of you has posted a platform[2], and announced your nomination to the developers. From this point, you are encouraged to ask each other questions about the posted platforms, and begin discussion of any points that you feel are particularly important during the next cycle. While you are not yet TC members, your voices and opinions about the issues raised in your platforms and questions raised by the wider community will help ensure that the future TC has the widest possible input on the matters of community concern, and the electorate has the best information to determine the ideal TC composition to address these and other issues that may arise. [1] https://governance.openstack.org/election/ [2] https://opendev.org/openstack/election/src/branch/master/candidates/2026.2/…

1 0

[watcher][election][ptl] Douglas Viroel PTL candidacy for 2026.2
by Douglas Viroel 18 Feb '26

18 Feb '26

Hi all, I would like to announce my candidacy for Watcher PTL for the 2026.2 (Hibiscus) cycle. I started contributing to OpenStack during the Stein cycle in Manila project where I still assist with patch reviews, depending on the demand. Starting at 2025.1 release, I have been a Watcher contributor and maintainer, working with other contributors to revive the project and tackle many of the existing technical debts. In 2025.2 I started the effort to remove Eventlet from Watcher and in 2026.1, working as tact-sig, have been refactoring our CI, including our stable branches, to properly test patches in both check and gate pipelines. For the 2026.2 cycle, these are some of the priorities that I plan to focus on: Testing and CI/CD Coverage Improvements: * Support the implementation of new integration test in Watcher Dashboard * Expand test coverage for features, datasources, and/or integrations that remain untested in CI (e.g.: Audit Scope feature) * Start the effort on adding functional tests to Watcher * Continue improvements to check/gate pipelines for master and stable branches Scalability and Availability: * Support for osprofiler in Watcher to enable performance analysis at scale * Performance analysis in Action Plan parallelization OpenStack SDK Migration: * Support the migration effort started in 2026.1 to modernize the remaining integrations Eventlet Removal: * Make native threads the default thread mode in 2026.2 * Address performance gaps when running with native threading * Prepare for Eventlet deprecation in 2027.1 Thank you for your consideration. Douglas Viroel IRC: dviroel

1 0

[cinder] festival of reviews friday 2026-02-20
by Brian Rosmaita 18 Feb '26

18 Feb '26

Hello Argonauts, This is a reminder that the twice-monthly Cinder Festival of Reviews will be held at the end of this week on Friday 20 February. who: Everyone! what: The Cinder Festival of Reviews when: Friday 20 February 2026 from 1400-1600 UTC where: videoconf info on the etherpad etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews This recurring meeting, that happens on the first and third Friday of each month, can be placed on your calendar by using this handy ICS file: https://meetings.opendev.org/calendars/cinder-festival-of-reviews.ics See you there!

1 0

[nova][ci] nova-live-migration-ceph job failing 100%
by melanie witt 17 Feb '26

17 Feb '26

We have another gate blockage going on right now with the nova-live-migration-ceph job which began to fail sometime on 2026-02-12 on the master branch: https://zuul.opendev.org/t/openstack/builds?job_name=nova-live-migration-ce… failing in the post stage with errors: 2026-02-17 15:33:11.163476 | LOOP [run-evacuate-hook : Stop libvirtd on "controller"] 2026-02-17 15:33:14.016935 | controller | changed: "libvirtd.service" 2026-02-17 15:33:14.671190 | controller | changed: "libvirtd.socket" 2026-02-17 15:33:15.286503 | controller | ok: "libvirtd-admin.socket" 2026-02-17 15:33:15.922638 | controller | ok: "libvirtd-ro.socket" 2026-02-17 15:33:19.293538 | controller | changed: "virtlogd.service" 2026-02-17 15:33:19.918949 | controller | changed: "virtlogd-admin.socket" 2026-02-17 15:33:20.541634 | controller | changed: "virtlogd.socket" 2026-02-17 15:33:21.114233 | controller | ERROR: Item: virtlockd.service 2026-02-17 15:33:21.114481 | controller | { 2026-02-17 15:33:21.114549 | controller | "ansible_loop_var": "item", 2026-02-17 15:33:21.114602 | controller | "item": "virtlockd.service", 2026-02-17 15:33:21.114652 | controller | "msg": "Could not find the requested service virtlockd.service: host" 2026-02-17 15:33:21.114702 | controller | } 2026-02-17 15:33:21.673927 | controller | ERROR: Item: virtlockd-admin.socket 2026-02-17 15:33:21.674126 | controller | { 2026-02-17 15:33:21.674189 | controller | "ansible_loop_var": "item", 2026-02-17 15:33:21.674242 | controller | "item": "virtlockd-admin.socket", 2026-02-17 15:33:21.674332 | controller | "msg": "Could not find the requested service virtlockd-admin.socket: host" 2026-02-17 15:33:21.674388 | controller | } 2026-02-17 15:33:22.221836 | controller | ERROR: Item: virtlockd.socket 2026-02-17 15:33:22.222026 | controller | { 2026-02-17 15:33:22.222090 | controller | "ansible_loop_var": "item", 2026-02-17 15:33:22.222188 | controller | "item": "virtlockd.socket", 2026-02-17 15:33:22.222259 | controller | "msg": "Could not find the requested service virtlockd.socket: host" 2026-02-17 15:33:22.222363 | controller | } This might be related to a recent change in openstack/devstack-plugin-ceph that merged on Feb 12: https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/976279 The breakage is being worked on in the following proposed patches: https://review.opendev.org/q/topic:%22nova-livemigration-ceph%22 Please hold your rechecks if your patch has failed CI due to this issue. -melwitt

1 1

[OSSA-2026-002] OpenStack Nova: calls qemu-img without format restrictions for resize (CVE-2026-24708)
by Jeremy Stanley 17 Feb '26

17 Feb '26

========================================================================= OSSA-2026-002: Nova calls qemu-img without format restrictions for resize ========================================================================= :Date: January 17, 2026 :CVE: CVE-2026-24709 Affects ~~~~~~~ - Nova: <30.2.2, >=31.0.0 <31.2.1, >=32.0.0 <32.1.1 Description ~~~~~~~~~~~ Dan Smith from Red Hat reported a vulnerability in nova. By writing a malicious QCOW header to a root or ephemeral disk and then triggering a resize, a user may convince Nova's flat image backend to call qemu-img without a format restriction resulting in an unsafe image resize operation that could destroy data on the host system. Only compute nodes using the Flat image backend (usually configured with use_cow_images=False) are affected. Patches ~~~~~~~ - https://review.opendev.org/977104 (2024.2/dalmatian) - https://review.opendev.org/977103 (2025.1/epoxy) - https://review.opendev.org/977101 (2025.2/flamingo) - https://review.opendev.org/977100 (2026.1/gazpacho) Credits ~~~~~~~ - Dan Smith from Red Hat (CVE-2026-24708) References ~~~~~~~~~~ - https://launchpad.net/bugs/2137507 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-24709 -- Jeremy Stanley OpenStack Vulnerability Management Team https://security.openstack.org/vmt.html

1 2

[election][cloudkitty] PTL candidacy for the 2026.2 release cycle
by Rafael Weingärtner 17 Feb '26

17 Feb '26

Hi all, I would like to self-nominate for the role of PTL of CloudKitty for the 2026.2 release cycle. I have been PTL since the Victoria cycle and I am willing to continue in this role. I will keep working with existing contributors to maintain CloudKitty for their use cases and encourage the addition of new functionalities. I have opened the patch with my candidacy: https://review.opendev.org/c/openstack/election/+/977071 -- Rafael Weingärtner

1 0

Fw: Zuul8.0 is not posting logs url into Opendev review commit
by Vasudevan, Senthil 16 Feb '26

16 Feb '26

Hello Team, We recently upgraded our CI environment from Zuul 3 to Zuul 8. Post that Opendev stopped depicting cutom github url that is log_url: We come to know that Zuul 8 onwards the account used for the integration of opendev gerrit and local zuul should have reviewer access to post comment back into commits. Would you please suggest any workaround or solution available to overcome it. Regards, Senthil V ________________________________ From: Vasudevan, Senthil Sent: Friday, February 6, 2026 5:31 PM To: zuul-discuss(a)lists.zuul-ci.org <zuul-discuss(a)lists.zuul-ci.org> Subject: Zuul8.0 is not posting logs url into Opendev review commit Hello Team, We have Zuul CI servers for HPE Cinder and Manilia drivers. We had Zuul 3.0 version earlier that posted external logs URL successfully back into Opendev gerrit. Once we upgraded the Zuul to 8.0 version, the URL is not posted to Opendev review commits. Looks the account used for Zuul and Opendev integration(http credentials are used for the integration) needs reviewer permission for Zuul version 8 and above. So please let me know whether that is mandatory to have reviewer access and if there are any workaround to post the URL to Opendev gerrit. Thanks, Senthil V

1 0

[Neutron] Bug Deputy Report Feb 9 - Feb 16
by Miro Tomaska 16 Feb '26

16 Feb '26

Hello Neutron, Here is the list of bugs from February 9th until the 16th. *High:* https://bugs.launchpad.net/neutron/+bug/2141546 - Neutron cleans OVN static routes it does not own Assigned: Martin Morgenstern *Medium:* https://bugs.launchpad.net/neutron/+bug/2141648 - [OVN] Allowed address pair with VMAC is not working in ML2/OVN Assigned: Rodolfo Alonso https://bugs.launchpad.net/neutron/+bug/2141908 - Optimize ``neutron.common.ovn.acl.update_acls_for_security_group`` Assigned: Rodolfo Alonso *Undecided: * https://bugs.launchpad.net/neutron/+bug/2141745 - Port in admin down does not send vif plugged events to nova Edit Unassigned *RFE:* https://bugs.launchpad.net/neutron/+bug/2141626 - [RFE] Remote-managed PF Plugging in OVN Driver Assigned: Dmitrii Shcherbakov *Waiting for more data:* https://bugs.launchpad.net/neutron/+bug/2141526 https://bugs.launchpad.net/neutron/+bug/2141530 It would be great to see full logs, but the OP is also using a Rocky release which is EOL. I will ask if this is also an issue on maintenance releases. https://bugs.launchpad.net/neutron/+bug/2141784 - Trunk: not able to filter trunks by their status It seems to work for me on master, waiting for more information -- Miro Tomaska

1 0

[kolla-ansible] Migration from OVS to OVN
by Winicius Allan 16 Feb '26

16 Feb '26

Hi kolla o/ I was searching to see if Kolla currently supports migration from OVS to OVN, and I've found this email thread [1]. I'd like to know if this feature has been implemented, and if so, what the necessary steps are. [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032785.h… Best regards

3 3

April 2026 PTG Team Signup Kickoff
by Kendall Nelson 16 Feb '26

16 Feb '26

Hello Everyone! The next OpenInfra PTG[1] will take place April 20-24, 2026 and registration for the event is now open[2]! For those new to the community, or perhaps just need the reminder, the PTG is a semi-annual event where project teams come together to hash out important details for the next six-ish months during a concentrated set of meetings that often include code sprints, bug fixing, design discussion, and cross project collaboration. To sign your team up, you must complete the survey[3] by March 1st at 7:00 UTC. If your team is not interested in participating, there is no need to fill out the survey. The contact information (email and preferably also IRC nickname) in the form will be used to share important details with moderators about team signup and further logistics. To ensure you receive all communications please double check and submit *ACCURATE* information! If you are not on IRC, please get on the OFTC network[4] and join #openinfra-events as much of the coordination for the event will be done in the #openinfra-events channel. You are also encouraged to familiarize yourself with the PTGBot documentation[5] as well. If you have any questions, please reach out to ptg(a)openinfra.org! Information about signing up for time slots will be sent to moderators shortly after the team signup deadline. -Kendall (diablo_rojo) [1] PTG Site: https://openinfra.org/ptg/ [2] PTG Registration: https://ptg.openinfra.org/ [3] Team Survey: https://openinfrafoundation.formstack.com/forms/apr2026_ptg_survey [4] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [5] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst

1 1

February 4 Meeting Recap & Next Steps
by Kendall Nelson 15 Feb '26

15 Feb '26

Hello folks! Thank you for all your participation thus far - watching the previous recording, answering the last poll, attending the meetings, etc. Here is the recording from today's meeting for those that were unable to attend it live: https://zoom.us/rec/share/9vo8njF87mFdFQhsYdZzYBrY3DSfeuo5t2EJIxMdV4CCtslQs… If you do watch, I would encourage you to add your name and details to the etherpad where we took notes on today's meeting: https://etherpad.opendev.org/p/Digital-Sovereignty-WG The next meeting date and time is to be determined by you all! Here is the poll to vote <https://beta.framadate.org/polls/fe703653fdd969cbdaf4/1e0eba4bc789b7067aa1/…> on a date/time between Feb 17th, 18th, and 19th. *I will set the deadline to vote for the end of the previous week - February 13. * Lastly, I want to remind folks of the homework we discussed on the call - using some of the words and phrases we brainstormed (and any others that get added) to craft a stance on why OpenInfra and our projects are able to support digital sovereignty. For more information on this discussion, please watch the recording of the recent meeting. Thanks! -Kendall

1 4

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2026.1/R-6)
by Goutham Pacha Ravi 15 Feb '26

15 Feb '26

Hello Stackers, We're 6 weeks away from the date of the coordinated release of OpenStack 2026.1 "Gazpacho" [1]. We have a number of release deadlines scattered between this week and next, so it's an extremely busy time for project maintainers and our release management team. The nomination window for the combined TC and PTL elections is also closing this week (at 23:45 UTC on February 18, 2026) [2]. At last count, there were 27 project teams that still needed a PTL nominee. If you'd like to volunteer to be a PTL or if you think someone else should be, please ensure a nomination is submitted prior to the deadline. If you have questions regarding the process, please feel free to ask them on this mailing list or in the #openstack-election IRC channel on OFTC. The substantive governance activity in the past week was around the CI fixes concerning the regression in setuptools [3]. We've had to resurrect some "x-static" repositories in order for the OpenStack Dashboard project team to work around the changes from the upstream Python community. We're beginning to define the tested runtimes for the OpenStack 2026.2 "Hibiscus" release cycle [4]. Please take a look and give us your feedback. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee was held over IRC on February 10, 2026 [5]. We focused on our past action items, technical debt, and the ongoing election cycle. We have officially closed the chapter on Monasca by abandoning 173 open changes across several repositories, and conversely, we’re seeing a promising revival of Cyborg with a new PTL nominee and a fresh team structure. In the hope of staffing project teams that have a large cross-project impact, we've proposed PTL nomination directories for the Requirements and Oslo teams not just to solicit candidates, but to spark a discussion on how we better support these critical dependencies. We discussed navigating a "borked" gate due to the recent setuptools' pkg_resources deprecation [3]. While we are currently merging "band-aid" pins to restore CI stability on stable branches, the situation would have been significantly worse without the proactive work done by Stephen Finucane (stephenfin) and Takashi Kajinami (tkajinam) over the last few months. Their foresight has saved project teams from a much larger headache during the feature freeze rush that's underway. Finally, we called out to project teams to review the User Survey streamlining plan [6]. Our goal is to refine this feedback loop prior to the PTG in April [7] so we can make timely improvements. The next meeting of the OpenStack Technical Committee is on Tuesday, February 17, 2026. This meeting is being held at 0800 UTC, a time that's better suited for our contributors in the Eastern Hemisphere. Please feel free to add to the agenda on the meeting's wiki page, and thank you in advance for your participation [8]. === Governance Proposals === ==== Merged ==== - Add a script to abandon changes on retired repositories | https://review.opendev.org/c/openstack/governance/+/975594 - Onboard additional xstatic packages | https://review.opendev.org/c/openstack/governance/+/976513 ==== Open For Review ==== - Define testing runtime for 2026.2 release | https://review.opendev.org/c/openstack/governance/+/976691 - Revert "Revive os_monasca" | https://review.opendev.org/c/openstack/governance/+/974775 === Upcoming Events === - 2026-02-26: 2026.1 "Gazpacho" Feature Freeze / Milestone 3 - 2026-03-10: OpenInfra Board Meeting: https://board.openinfra.org/ - 2026-03-23: KubeCon+Cloud Native Con EU begins: https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/ - 2026-04-20: OpenInfra PTG begins: https://openinfra.org/ptg/ === How to Contact the TC === You can reach the TC in several ways: 1. Email: send an email with the tag [tc] on this mailing list. 2. Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC. 3. Join us at our weekly meeting: The Technical Committee meets every Tuesday at 1700 UTC, except the third Tuesday of the month, when we meet at 0800 UTC [8]. Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2026.1 "Gazpacho" Release Schedule: https://releases.openstack.org/gazpacho/schedule.html [2] OpenStack "2026.2" Elections: https://governance.openstack.org/election/ [3] setuptools regression: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [4] Tested runtimes for 2026.2: https://review.opendev.org/c/openstack/governance/+/976691 [5] TC Meeting IRC Log, February 10 2026: https://meetings.opendev.org/meetings/tc/2026/tc.2026-02-10-17.00.html [6] Streamlining the OpenStack User Survey: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [7] OpenInfra PTG: https://openinfra.org/ptg/ [8] TC Meeting Agenda, February 17 2026: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[all][elections][ptl][tc] Combined PTL/TC 2026.2 cycle Election Nominations Last Days
by Ian Y. Choi 13 Feb '26

13 Feb '26

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Feb 18, 2026 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at[1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. All members of the community are encouraged to confirm their email address and opt in to the CIVS election as described at: https://governance.openstack.org/election/#electorate Election statistics[2]: Nominations started @ 2026-02-04 23:45:00 UTC Nominations end @ 2026-02-18 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 5 days, 0:17:37 Nominations progress : 64.20% --------------------------------------------------- Projects[1] : 40 Projects with candidates : 13 ( 32.50%) Projects with election : 1 ( 2.50%) --------------------------------------------------- Need election : 1 (Horizon) Need appointment : 27 (Adjutant Barbican Cinder Cloudkitty Heat Keystone Masakari Mistral Neutron Octavia OpenStackAnsible OpenStackSDK OpenStack_Charms Oslo Puppet_OpenStack Quality_Assurance Rally Requirements Skyline Storlets Sunbeam Swift Tacker Trove Venus Vitrage Zun) --------------------------------------------------- TC Candidates : 2 (5 Required) =================================================== Stats gathered @ 2026-02-13 23:27:23 UTC This means that with approximately 2 days left, 27 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.opendev.org/q/project:openstack/election+is:open+file:candid… have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

[manila][election][ptl] Carlos da Silva Candidacy for 2026.2 PTL
by Carlos Silva 13 Feb '26

13 Feb '26

Hello, I would like to announce my candidacy for Manila PTL for the 2026.2 (Hibiscus) cycle. I have been serving as Manila PTL for the past couple of releases and am happily investing time and energy into working with this very talented and passionate group of contributors. Over these releases, we have been creating more and more opportunities for contribution, ranging from code to involving cloud users and operators in our discussions to collect feedback. This helps us deliver valuable enhancements and fixes. We still have lots to do, and that includes enhancing our contributor experience. Therefore, in the upcoming cycle, I would like to direct our focus to: Eventlet: python-manilaclient is successfully migrated. We are now completing the migration in the manila code base, so we will focus on finalizing it and testing the changes we are making while moving away from eventlet. Tech debt: Continue the efforts to reach parity between Manila APIs and Manila UI, and complete the rootwrap -> privsep migration. VirtioFS: Closing the scenario testing gap for VirtioFS. Mentorship: Continue shepherding and encouraging more active reviewer participation and preparing new core reviewers. Communication: Reshaping the way we communicate and document our team priorities. Thank you for your consideration. Carlos da Silva IRC: carloss

2 1

[release] Release countdown for week R-6
by Thierry Carrez 13 Feb '26

13 Feb '26

Development Focus ----------------- Work on libraries should be wrapping up, in preparation for the various library-related deadlines coming up. Now is a good time to make decisions on deferring feature work to the next development cycle in order to be able to focus on finishing already-started feature work. General Information ------------------- We are now getting close to the end of the cycle, and will be gradually freezing feature work on the various deliverables that make up the OpenStack release. This coming week is the deadline for general libraries (except client libraries): their last feature release needs to happen before "Non client library freeze" on February 19th, 2026. Only bugfixes releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2026.1 branching request with the review (as an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… In the next weeks we will have deadlines for: * Client libraries (think python-*client libraries), which need to have their last feature release before "Client library freeze" (February 26th, 2026) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, February 26th, 2026. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. As we are getting to the point of creating stable/2026.1 branches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/2026.1 branches are cut for a repo, the ability to approve any necessary backports into those branches for 2026.1 "Gazpacho" will be limited to the members of that stable team. If there are any questions about stable policy or stable team membership, please reach out in the #openstack-stable channel. Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 19th, 2026 (R-6 week) Client library freeze: February 26th, 2026 (R-5 week) Gazpacho-3 milestone: February 26th, 2026 (R-5 week) Cycle Highlights Due: March 5th, 2026 (R-4 week) 2026.1 "Gazpacho" final release: April 1st, 2026 2026.2 "Hibiscus" (virtual) PTG: April 20-24, 2026 -- Thierry Carrez (ttx)

1 0

[neutron][ovn-bgp-agent] Fix for missing /etc/iproute2/rt_tables after iproute2 upgrade
by Maximilian Stinsky-Damke 13 Feb '26

13 Feb '26

Hi everyone, I wanted to bring attention to an issue that affects ovn-bgp-agent deployments after upgrading to newer versions of the iproute2 package. Problem: In newer iproute2 package versions, the default rt_tables file has been moved from /etc/iproute2/rt_tables to /usr. This change was introduced as part of iproute2's move to a "stateless" configuration pattern where configuration files are read from /etc first, falling back to /usr if they don't exist. You can see the related iproute2 commit here: https://github.com/iproute2/iproute2/commit/0a0a8f12fa1b03dd0ccbebf5f85209d… When iproute2 is upgraded on Rocky Linux (and other RHEL-based systems), if /etc/iproute2/rt_tables was modified, it gets moved to /etc/iproute2/rt_tables.rpmsave and the original file isn't recreated. See https://access.redhat.com/solutions/7123966 for more details. I suspect Debian-based systems have the same issue. The ovn-bgp-agent has a hard requirement on /etc/iproute2/rt_tables existing, which causes it to fail with a FileNotFoundError when it attempts to read the file: FileNotFoundError: [Errno 2] No such file or directory: '/etc/iproute2/rt_tables' The error occurs in ensure_routing_table_for_bridge() when the agent tries to check for existing routing table entries for bridges. Proposed Solution: I've proposed a fix that ensures the /etc/iproute2/rt_tables file exists before attempting to read it. The solution: 1. Creates a new privileged function ensure_routing_tables_file() that: - Creates the /etc/iproute2/ directory if it doesn't exist - Copies the default rt_tables file from /usr/share/iproute2/rt_tables to /etc/iproute2/rt_tables if the latter doesn't exist 2. Calls this function before reading rt_tables in ensure_routing_table_for_bridge() This approach maintains backward compatibility while handling the new iproute2 package structure gracefully. Bug Report: https://bugs.launchpad.net/ovn-bgp-agent/+bug/2141421 Proposed Patch: https://review.opendev.org/c/openstack/ovn-bgp-agent/+/976242 Has anyone else hit this issue? We didn't find any upstream fix for it yet, so we'd appreciate feedback on the patch. Thanks, Max

1 0

[neutron] Drivers meeting canceled Friday, February 13th
by Brian Haley 12 Feb '26

12 Feb '26

Hello Neutrinos: I am going to cancel tomorrow's Drivers meeting as there are no topics on the agenda. Just a reminder that our open spec list is at [0]. Have a nice weekend! -Brian [0] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

[charms][sunbeam] Proposing Ahmad Hassan for sunbeam-core
by Guillaume Boutry 12 Feb '26

12 Feb '26

Hi all, Ahmad has been working for a year actively on Sunbeam charms and has proven to be an able reviewer and contributor. I'd like to propose Ahmad as a member of the sunbeam-core team. Cheers, Guillaume

3 2