February 2026 - openstack-discuss

[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

[tc][election] gouthamr's TC Candidacy for 2026.2
by Goutham Pacha Ravi 11 Feb '26

11 Feb '26

Hello Stackers, I am submitting my candidacy for another term on the OpenStack Technical Committee. It's been two years since I was first elected, and I've served as TC Chair during this time. In these past two years, we've gotten some important things done: the CLA-to-DCO transition that our community asked for over a decade ago, extending the VMT's mandate to all project teams, setting clear expectations around project retirements and governance transitions, and consolidating our governance repositories. I'm proud of this work, and I'm running again because there's more to do. One thing that has become clear to me as Chair is that the people who keep OpenStack running by fixing gates, reviewing code across projects, reporting and triaging bugs, maintaining infrastructure and other myriad things don't get enough recognition for it. I'm hoping to change that by creating an objective, tangible way to acknowledge valuable contributions and enthuse our community to do more of this work. We are one of the largest open source projects in the world, and the community that's responsible for it is a bedrock needs constant care. I also want the TC to stay engaged with where cloud infrastructure is headed. OpenStack should be the free and open source choice for Sovereign Clouds and AI workloads. We'd do this not by chasing trends, but by ensuring our project teams are equipped and positioned for these use cases as they mature. On the governance side, I'll keep working to eliminate bottlenecks that slow our project teams down while maintaining the consistent maintenance model that has made our successful projects sustainable. The Technical Vision for OpenStack Clouds hasn't been modified in a while, and I'd like to help draft its next iteration. I'll take the opportunity to also include a process for evolving it. Lastly, two years on the TC have shown me how much we benefit from experienced, engaged leaders across our projects. I want to build mentoring pathways for future TC members, so our leadership pipeline is as durable as the software we produce. Thank you for your consideration. Goutham Pacha Ravi (gouthamr) Affiliation: Red Hat Inc. OpenInfra Profile: https://openinfra.dev/a/community/members/35705 Nomination: https://review.opendev.org/c/openstack/election/+/976553

1 0

[ci][nova][cinder][glance][devstack][swift] openstacksdk-functional-devstack job failing 100%
by melanie witt 11 Feb '26

11 Feb '26

Hey all, We noticed sometime today the openstacksdk-functional-devstack job appears to be failing 100% in multiple projects: https://zuul.opendev.org/t/openstack/builds?job_name=openstacksdk-functiona… The failing openstacksdk test is test_add_remove_router_interface [1]: ft1.1: openstack.tests.functional.cloud.test_router.TestRouter.test_add_remove_router_interfacetesttools.testresult.real._StringException: Traceback (most recent call last): File "/home/zuul/src/opendev.org/openstack/openstacksdk/openstack/tests/functional/cloud/test_router.py", line 232, in test_add_remove_router_interface self.assertIn(key, iface) File "/home/zuul/src/opendev.org/openstack/openstacksdk/.tox/functional/lib/python3.12/site-packages/testtools/testcase.py", line 425, in assertIn self.assertThat(haystack, Contains(needle), message) File "/home/zuul/src/opendev.org/openstack/openstacksdk/.tox/functional/lib/python3.12/site-packages/testtools/testcase.py", line 509, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: 'tenant_id' not in {'id': '57671080-6eb2-4c7f-9e64-c61edfa8995e', 'project_id': '1ef2e6c3fc2d4f6b92fdd8d49f0a05a1', 'port_id': '5b39bbfc-6d3d-440e-9c7a-e56e434ef897', 'network_id': '8aa6b6e2-e0c5-4f96-bb87-5509e30d340c', 'subnet_id': '6f52d8be-cf68-4552-b57d-37142cea65cc', 'subnet_ids': ['6f52d8be-cf68-4552-b57d-37142cea65cc']} which adds an interface to a router and expects the response parameter 'tenant_id' to be in the response. I looked for recently merged changes that could have possibly changed the router API response and it might be something similar to this change: https://review.opendev.org/c/openstack/neutron/+/972982 but I don't really understand if/how that could change the API. I'm not sure what the desired fix will be here, whether the API should be more backward compatible and/or if the openstacksdk test should be fixed by s/tenant_id/project_id/ or something else. Please hold your rechecks if CI has failed on your patch due to this. -melwitt [1] https://github.com/openstack/openstacksdk/blob/7afe210333ec236a14fc5fa2d4a5…

3 5

[ci][kolla] setuptools v82.0.0 breaks a bunch of things by removing pkg_resources
by Michael Still 11 Feb '26

11 Feb '26

Hey all, I've just noticed that setuptools v82.0.0 released todayish and breaks a bunch of Kolla builds (and probably other things) by removing pkg_resources. https://setuptools.pypa.io/en/stable/history.html#v82-0-0 has further details of the release. setuptools doesn't seem to be listed in upper-constraints, perhaps because it's often provided as a distro package? Michael

9 16

How to access OpenStack instances from the bastion node when deploying OpenStack using Kolla-Ansible
by ussefelboukhari＠gmail.com 11 Feb '26

11 Feb '26

In test environments, some users choose to build their infrastructure inside KVM virtual machines, while others use cloud instances such as EC2 bare-metal that support nested virtualization. After deploying OpenStack, many of them face a major issue: they are unable to access their OpenStack instances. I encountered the same problem myself. After several weeks of intensive troubleshooting, I eventually found a solution. That is why I would like to share this solution with others who face the same issue, and hopefully contribute to the OpenStack community by providing recommendations that could be added to the official OpenStack documentation.

2 1

[nova][elections][ptl] Application for the PTL role 2026.2
by René Ribaud 11 Feb '26

11 Feb '26

Hello, After serving as PTL for Flamingo and Gazpacho, I would like to announce my candidacy for the 2026.2 (Hibiscus) Nova and Placement PTL role. The previous cycle was somewhat unusual, as upstream contributions from several core contributors were impacted by internal changes within their organizations. Despite this, the community stayed engaged and resilient, and I am grateful for everyone who kept things moving forward. The Eventlet removal effort, which started earlier and significantly progressed during Flamingo and Gazpacho, should reach completion this cycle. This will be an important milestone and will allow us to introduce new changes more confidently. In 2026.2, I would like to focus on enabling forward-looking work such as confidential computing improvements, restarting collaboration with Manila around virtiofs, and further I/O performance improvements. The concrete priorities and scope of these efforts will be discussed and refined during the next PTG. In parallel, I will continue to improve review efficiency and maintain a welcoming and focused community. My goal remains simple: keep Nova and Placement robust, maintainable, and aligned with our users’ needs. I would be honored to continue serving in this role. Thanks, René

1 0

[kolla-ansible][rabbitmq] RabbitMQ cluster creation took too long
by Nguyễn Hữu Khôi 10 Feb '26

10 Feb '26

Hello. I am deploying OpenStack 2025.1 with Kolla-Ansible 2025.1 (master branch) using the latest images. However, when I created a RabbitMQ(4.0.x) cluster with 3 nodes, it took too long—around 12 minutes(it stucked at DB: virgin node -> run peer discovery). I then changed the images to RabbitMQ version 3.13.7, and it worked well. My OS: Ubuntu 24.01 Nguyen Huu Khoi

2 2

[ops][publiccloud-sig] Public Cloud SIG meeting d.d. 11 February
by Kees Meijs | Nefos 10 Feb '26

10 Feb '26

Hello Stackers, Tomorrow (that's 11 February) the bi-weekly Public Cloud SIG meeting will be held again. The publicly available video meeting will be conducted from 08:05 hrs UTC (09:05 hrs CET) until 08:55 hrs UTC (09:55 hrs CET) here: https://meetpad.opendev.org/publiccloud-sig Additional information to be found on https://wiki.openstack.org/wiki/PublicCloudSIG See you tomorrow! Cheers, Kees __ Kees Meijs BICT Nefos Cloud & IT <https://nefos.com/contact> Nefos IT bv Burgemeester Mollaan 34a 5582 CK Waalre - NL kvk 66494931 +31 (0)88 2088 188 <tel:+31882088188> nefos.com <https://nefos.com/contact> The information contained in this message is intended for the addressee only and may contain classified information. If you are not the addressee, please delete this message and notify the sender; you should not copy or distribute this message or disclose its contents to anyone. Any views or opinions expressed in this message are those of the individual(s) and not necessarily of the organization. No reliance may be placed on this message without written confirmation from an authorised representative of its contents. No guarantee is implied that this message or any attachment is virus free or has not been intercepted and amended. General terms and conditions ("The NLdigital Terms") apply to all our products and services.

1 0

How to change flavor or sg of a virtual machine with Ansible?
by Marco Favero 10 Feb '26

10 Feb '26

Hello, I'm new in this Openstack world and I love Ansible. I'm trying to use the openstack.cloud Ansible collection to manage virtual machines. There is no problems in adding or deleting a virtual machine (vm). The openstack.cloud.server module works very well. I'm in trouble if I want to update a vm. The server module has only the "present" state: the resource is not updated after the creation if I change something in the module parameters. So, I can't use openstack.cloud.server module in order to change the flavor or security group of an already existing vm. The "server_action" module is not useful because it has not update actions about sg or flavor. I tried the CRUD "resource" module in some way such as --- - name: Change resources hosts: localhost tasks: - name: Change flavor to vm openstack.cloud.resource: cloud: myStack service: compute type: server attributes: name: vm-name flavor_id: 22b4d2c2-0fff-437b-a67c-009244f89403 state: present wait: true but the play fails with fatal: [localhost]: FAILED! => {"changed": false, "extra_data": {"data": null, "details": "Invalid input for field/attribute server. Value: {'flavorRef': '22b4d2c2-0fd8-437b-a67c-009244f89403'}. Additional properties are not allowed ('flavorRef' was unexpected)" If I try with "flavor" or "security_groups" attributes in place of "flavor_id" the error doesn't change. Could you help me? My env is: [root@cnt-ansible]/workdir/openstack# ansible-galaxy collection list | grep openstack openstack.cloud 2.5.0 [root@cnt-ansible]/workdir/openstack# pip3 list | grep openstack openstacksdk 4.9.0 ansible [core 2.16.14] Thank you very much Kind Regards Marco

5 5

[neutron] Bug Deputy Report Feb 02 - Feb 09
by Terry Wilson 10 Feb '26

10 Feb '26

Hi Neutrinos, Below is the bug deputy report for last week: High ==== * https://bugs.launchpad.net/neutron/+bug/2141304 - [oslo master] neutron-periodic-workers crashing with ERROR neutron AttributeError: Can't pickle local object 'Mapper.__init__.<locals>.<lambda>' - Unassigned Medium ====== * https://bugs.launchpad.net/neutron/+bug/2139583 - neutron-openvswitch-agent native driver: Permanent flow loss after OVS restart due to unhandled 'unknown dpid' during rpc_loop - Unassigned - As Yatin mentioned last week, it looks valid. Reporter attached the requested logs and points to the code they think is responsible. * https://bugs.launchpad.net/neutron/+bug/2139581 - Updating router state fails due to NoneType error - Assigned to William Tripp - Patch uploaded by Rodolfo - https://review.opendev.org/c/openstack/neutron/+/975373 * https://review.opendev.org/c/openstack/neutron/+/975373 - TapMirrorPlugin should not allow execution of non implemented TaasPlugin methods - Assigned to Miro Tomaska * https://bugs.launchpad.net/neutron/+bug/2140291 - [network_segment_range] VM creation fails with a KeyError - Assigned to Kyuyeong Lee * https://bugs.launchpad.net/neutron/+bug/2141308 - ``LoggingServiceDriverManager`` should handle the update of ``rpc_required`` - Assigned to Rodolfo - Patch https://review.opendev.org/c/openstack/neutron/+/976130 Low === * https://bugs.launchpad.net/neutron/+bug/2140762 - Define a reasonable default value for the OVN FDB aging and removal limit - Assigned to Rodolfo, - Patch https://review.opendev.org/c/openstack/neutron/+/975908 * https://bugs.launchpad.net/neutron/+bug/2141320 - [neutron-fwaas] The FWaaS plugin is always loading the ``IptablesLoggingDriver`` - Unassigned

1 0

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

09 Feb '26

Hello Stackers, We're 7 weeks away from the date of the coordinated release of OpenStack 2026.1 "Gazpacho" [1]. At the end of this week, Oslo libraries and python-openstackclient will observe a feature-freeze until we are past the coordinated release. Project teams are busy reviewing feature changes in "cycle-with-rc" deliverables [2] with the hope to observe feature freeze in two weeks (February 26, 2026). In the past week, the OpenStack Technical Committee reset the leadership model for the Oslo and Requirements project teams. This means that these project teams could nominate and elect a PTL during the ongoing elections [3]. We do this with cautious optimism to indicate to the wider community that project governance is hard and it's extremely valuable. Oslo and Requirements are two project teams that maintain deliverables that affect nearly every other OpenStack project. However, we've only at best received part-time interest in their maintenance. Project liaisons have told the TC that they would really like help in the form of newer maintainers. If you're thinking about joining these project teams and lending a hand, please let us know. In a similar vein, over the past several weeks, the TC has noted that the FIPS compliance goal has degraded in its purpose [4]. In the past few release cycles, more work has been put into maintaining test jobs and this has threatened to divert our limited resources. The effort to pull together testing across OpenStack projects has turned out to be too large for an individual to handle. Therefore, we've dropped the cross-community goal for the moment. For it to be revived, we would need a level of commitment from a team of individuals, a clear definition of what can be tested, how the tests will function, and who would maintain them. We understand that FIPS compliance can be essential for a subset of organizations or countries that OpenStack serves. The TC doesn't seek to push back on the goal, but we need specifics and resources that we can't dedicate at the moment. As a consequence, project teams can choose to tear down existing jobs, or choose to maintain them using their best judgment. Finally, the elections are underway. We are seeking nominations for 5 seats on the OpenStack Technical Committee and for PTLs across project teams, with the exception of the Freezer, Ironic, and Release Management teams that have decided to follow a Distributed Leadership Model for the 2026.2 release cycle. If you wish to nominate yourself, please note that the nominations need to be accepted by 23:45 UTC on February 18, 2026 [3]. I hope you are able to verify your eligibility to be a part of the electorate as well [5]. === Weekly Meeting === The OpenStack Technical Committee meeting on February 3, 2026 focused on our feedback loop on project health as we approach the Gazpacho Feature Freeze [6]. We discussed the OpenStack User Survey with Allison Price (aprice), VP of Marketing & Community at the OpenInfra Foundation. We've concluded that the survey’s current complexity has become a barrier for operators; our goal is to rebuild it from a clean slate. A thought was to move to an opt-in model for questions with which we can deliver a leaner, more impactful survey by August 2026. We hope that the survey will provide PTLs with actionable data rather than just historical noise. I encourage all project leads/liaisons to participate in the upcoming feedback sessions to ensure the insights you actually need for development are prioritized. [7] On the technical and governance front, we're supporting the revival of Cyborg by resolving Launchpad ownership issues and ensuring the team has the necessary core permissions to land release-critical patches before M-3. We also addressed the reality of declining synchronous meeting attendance in projects like Barbican; while we are comfortable with teams moving to ad-hoc or asynchronous coordination to match their contributor velocity, the TC remains firm that design discussions must stay public and logged. Finally, we discussed the ongoing elections and the difficult and thankless job of maintaining cross-functional project teams like Requirements, Oslo, and Release Management. A hat tip to you folks that volunteer to do this! The next meeting of the OpenStack Technical Committee is on Tuesday, February 10, 2026. It will be hosted on the #openstack-tc IRC channel on OFTC. Please find the agenda on the meeting's wiki page [8]. I hope you'll be able to join us there. === Governance Proposals === ==== Merged ==== - Move FIPS Compliance goal back to proposed | https://review.opendev.org/c/openstack/governance/+/969145 - Reset the DPL model for Oslo project | https://review.opendev.org/c/openstack/governance/+/974929 - Reset the DPL model for requirements project | https://review.opendev.org/c/openstack/governance/+/974927 ==== Open For Review ==== - Add a script to abandon changes on retired repositories | https://review.opendev.org/c/openstack/governance/+/975594 - Revert "Revive os_monasca" | https://review.opendev.org/c/openstack/governance/+/974775 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] Cycle with RC release model: https://releases.openstack.org/reference/release_models.html#cycle-with-rc [3] OpenStack "2026.2" Elections: https://governance.openstack.org/election/ [4] FIPS compliance goal dropped back to "proposed": https://governance.openstack.org/tc/goals/proposed/fips.html [5] Check your eligibility to vote: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [6] https://meetings.opendev.org/meetings/tc/2026/tc.2026-02-03-17.00.html [7] Streamlining the OpenStack User Survey: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [8] TC Meeting Agenda, February 10 2026: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[cyborg] Restarting Weekly Cyborg IRC Meetings
by Ronelle Landy 09 Feb '26

09 Feb '26

Hello All, We would like to restart the weekly Cyborg IRC meetings on the #openstack-cyborg channel. Meetings were previously held on Fridays at 0600UTC - 0700UTC. Previous meetings notes can be found at [1]. Noting the graphical distribution of the initial engineers who wish to start contributing, there is a proposal to move the meetings to Tuesdays 14:00 -15:00 UTC. If there are no objections, the IRC meetings will start on Tuesday, February 17th at 14:00 UTC. Please join the discussions on channel and the meetings if you wish to contribute. Thank you, Ronelle [1] https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Agenda

1 1

[Nova] Live migration failed / VM has latency with patch to add managed='no' flag to libvirt XML
by Chang Xue 09 Feb '26

09 Feb '26

Hi, We are upgrading from Jammy to Noble, and need to include the patch https://review.opendev.org/c/openstack/nova/+/967570?tab=comments so VMs could be created on Noble nodes. However, all of our existing VMs that were created without the patch could not be live migrated to Noble, and has latency in live migrating to Jammy WITH the patch. To be clear: Old VMs created on Jammy -> patch applied on Jammy and Noble -> VMs can be live migrated to Jammy now, but with latency (VMs are pingable almost 10 seconds after live migration completed); VMs can not be live migrated directly to Noble nodes. After live migrated to Jammy with latency, we could live migrate the VMs between Jammy nodes, and one-way to Noble nodes, without any latency. Would like to understand it more, is there any way to get rid of the latency issue? I tried to patch nova/virt/libvirt/migration.py to add managed='no' flag when migration is on fly, but it only allows me to live migrate the old VMs directly to Noble nodes, latency still exists. Thanks, Chang

4 11

[cinder][nova][os-brick] Guidance on cross-project driver contribution
by Alokedip Choudhuri 08 Feb '26

08 Feb '26

Hello Everyone, We are working on contributing a new Cinder driver for *Infoscale*. This implementation requires coordinated changes across three projects to support the full attachment lifecycle: 1. *Cinder:* The core driver implementation. 2. *os-brick:* The connector APIs have been implemented there 3. *Nova:* New driver implementation to support the required operations like, "attach, detach, extend" for the volumes provisioned through the InfoScale Backend. We have already registered blueprints for this work: - *Cinder Blueprint:* https://blueprints.launchpad.net/cinder/+spec/infoscale-cinder-driver - *Nova Blueprint:* https://blueprints.launchpad.net/nova/+spec/infoscale-nova-driver Since this is a cross-project effort, I would appreciate guidance on the preferred workflow for submitting patches across multiple repositories to ensure a smooth integration. Looking forward to your feedback and suggestions. Thanks & Regards Alokedip

3 2

[keystone] Questions about federation mapping rules for academic research
by Sait, Abubakur Abdulgader S 07 Feb '26

07 Feb '26

Hello Keystone community, I am a PhD student researching privacy in federated identity systems. My work focuses on OpenStack Keystone federation, specifically how mapping rules process attributes from external Identity Providers. I would appreciate any insights from operators or developers about real-world federation deployments. My questions are: About mapping rules: 1. How many mapping rules do you typically have per federated IdP? 2. How often do these rules change after initial deployment? 3. Do you commonly use regex conditions, or mostly exact match conditions like any_one_of and not_any_of? About attributes: 4. How many attributes do you typically receive from federated IdPs? 5. For multi-valued attributes, how many values does a typical user have? About privacy: 6. Do you have privacy requirements affecting federated attributes? Any response would help my research. I am happy to share findings with the community when completed. Thank you for your time. Best regards, Abubakur Sait PhD Student, Wright State University, Dayton, OH, USA

1 0

[all][election] Check your voting eligibility for the OpenStack PTL & TC elections
by Goutham Pacha Ravi 06 Feb '26

06 Feb '26

Hello Stackers, Election season is here, and we want to ensure every voice that helps build OpenStack is heard. I would like you to take a moment to verify your "Active Contributor" [1] and OpenInfra Foundation membership status so you don't miss your chance to vote. To receive a ballot for the OpenStack TC elections, you must be a contributor to OpenStack repositories _and_ hold the status of "OIF Individual Member." To receive a ballot for a PTL election, you must have contributed to any of a project team's repositories _and_ hold the status of "OIF Individual Member." Check your membership level: ======================== Log in to your profile at https://openinfra.org/a/profile. Even if you’ve been a member for years, the OpenInfra Foundation (OIF) has a policy that automatically downgrades memberships to "OIF Community Member" if you haven't voted in recent Governing Board elections [2]. Upon logging in, if you see that you are an "OIF Community Member," you can restore your "OIF Individual Member" status on that profile page. Get recognized as an "Active Contributor": ================================ While our policy traditionally focuses on contributors to OpenStack's git repositories, we know that impactful work happens far beyond just code and documentation. We definitely value the "intangible" work that keeps this community running. If you haven’t contributed code or documentation to a repository during the 2025.2–2026.1 timeframe (March 14, 2025 – February 18, 2026), you can still vote! Please reach out to the PTL or DPL liaison of the project team you’ve supported and request to be added as an "Extra AC" (Extra Active Contributor) today [3]. The deadline to do this is February 13, 2026. If you run into issues or have questions about your eligibility, the TC would be happy to help. Simply reply to this thread, or chime in on OFTC's #openstack-tc IRC channel. Thanks, Goutham Pacha Ravi (gouthamr) [1] "Active Contributor": https://governance.openstack.org/tc/reference/charter.html#voters-for-tc-se… [2] OIF membership page: https://openinfra.org/join/individual/ [3] Extra AC deadline: https://releases.openstack.org/gazpacho/schedule.html#g-extra-acs

5 6

[release] Release countdown for week R-7
by Thierry Carrez 06 Feb '26

06 Feb '26

Development Focus ----------------- We are entering the last weeks of the 2026.1 " Gazpacho" development cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-AC freeze, in preparation for elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Contributor and allowed to vote. This is done by adding extra-acs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-AC freeze on February 12th. A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * Oslo libraries are entering feature freeze next week, February 12th. * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (February 19th). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 26th) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 26th. Any feature addition beyond that date should be discussed on the mailing list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (March 12th) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (March 26th) Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to one week after Feature freeze (March 5th). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… jeremy [at] openstack.org/fungi on IRC is available if you need help selecting or writing your highlights. Upcoming Deadlines & Dates -------------------------- Extra-AC freeze: February 12th, 2026 (R-7 week) Oslo feature freeze: February 12th, 2026 (R-7 week) 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 deadline: March 5th, 2026 (R-4 week) Hibiscus (virtual) PTG: April 20-24, 2026 -- Thierry Carrez (ttx)

1 0

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

05 Feb '26

Hello Neutrinos: I am going to cancel tomorrow's Drivers meeting as there are no topics and I will be out. 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][cinder] strange behavior with 2 storage nodes
by Alexander Luedtke 05 Feb '26

05 Feb '26

Hello Everyone, I have an strange behavior here on an cinder installation deployed with Kolla: The Setup: - 1 Controller node - some compute nodes - 2 Storage nodes (storage0, storage2) - later it should be 3. both with NFS Setup what is working. both storage nodes are shown on Skyline. The Problem: 1. in Skyline both storage nodes are shown but both are shown with the same size of one of both. 2. When I created a Volume then it was created on the other host as shown (in DB, skyline and so on) Anyone an idea what I can do to correct this problems ? Thanks a lot for your help ! Alexander -- Alexander Luedtke Systemadministrator Technische Universität München TUM School of Computation, Information and Technology Chair of IT Security Garching Boltzmannstr. 3 Room 01.08.036 85748 Garching b. Muenchen Tel. +49 89 289 18039 www.sec.in.tum.de

1 1

[policy] Updating RBAC (policy-popup team) meeting time
by Ghanshyam Maan 05 Feb '26

05 Feb '26

Hello Everyone, I have a conflict at the current time, so I am rescheduling the RBAC meeting to an hour later. Monday, Monthly 17:00 UTC. -> Monday, Monthly 18:00 UTC. I will update the wiki and the ICS file. Details: https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… ICS File: https://meetings.opendev.org/#Secure_Default_Policies_Popup-Team_Meeting -gmann

1 0

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

05 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 6 February. who: Everyone! what: The Cinder Festival of Reviews when: Friday 6 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

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

05 Feb '26

Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (5 positions) are now open and will remain open until Feb 18, 2026 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/2026.2/<Project_Name or "TC">/<email_address> (for example, "candidates/2026.2/TC/stacker(a)example.org"). The name of the file should match an email address for your current Foundation Individual Membership. Take this opportunity to ensure that your Open Infrastructure Foundation member profile contains current information: https://openinfra.org/a/profile Any Open Infrastructure Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an Open Infrastructure Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the 2025.2 to 2026.1 timeframe, Mar 14, 2025 00:00 UTC - Feb 18, 2026 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Feb 25, 2026 23:45 UTC through to Mar 18, 2026 23:45 UTC. The electorate for the TC election are the Open Infrastructure Foundation Individual Members who have a code contribution to one of the official teams over the 2025.2 to 2026.1 timeframe, Mar 14, 2025 00:00 UTC - Feb 18, 2026 00:00 UTC, as well as any Extra ACs who are acknowledged by the TC. The electorate for a PTL election are the Open Infrastructure Foundation Individual Members who have a code contribution over the 2025.2 to 2026.1 timeframe, Mar 14, 2025 00:00 UTC - Feb 18, 2026 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ACs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ACs. Please find below the timeline: PTL + TC nomination starts @ Feb 04, 2026 23:45 UTC PTL + TC nomination ends @ Feb 18, 2026 23:45 UTC TC campaigning starts @ Feb 18, 2026 23:45 UTC TC campaigning ends @ Feb 25, 2026 23:45 UTC PTL + TC elections start @ Feb 25, 2026 23:45 UTC PTL + TC elections end @ Mar 18, 2026 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2026-02-18 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and Foundation individual member profiles can be updated at https://review.opendev.org/#/settings/contact and https://openinfra.org/a/profile accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials

1 0

[nova][ci] nova-next job is failing 100%
by melanie witt 05 Feb '26

05 Feb '26

Hey all, Just a heads up that we currently have a 100% fail rate broken nova-next job due to the following bug: https://bugs.launchpad.net/cinder/+bug/2127196 Fixes on both the Cinder and Nova side are proposed: * https://review.opendev.org/c/openstack/cinder/+/975540 * https://review.opendev.org/c/openstack/nova/+/975542 Please hold your rechecks until at least one of these patches is merged. Cheers, -melwitt

1 1

[qa][ptg] Call for 2026.2 vPTG QA topic
by Ghanshyam Maan 04 Feb '26

04 Feb '26

Hi All, I have created the etherpad to collect the QA topics for the coming vPTG (2026.2 cycle). Based on the topics, we will decide if we need any slots in PTG. Seeing the PTG signup deadline, please add your topics before Feb 17th so that we can discuss the same in Feb 18th QA office hour. - https://etherpad.opendev.org/p/qa-2026.2-ptg -gmann

1 0

[all][elections][ptl][tc] Combined PTL/TC 2026.2 cycle Election Season
by Ian Y. Choi 04 Feb '26

04 Feb '26

Election details: https://governance.openstack.org/election/ The nomination period officially begins Feb 04, 2026 23:45 UTC. Please read the stipulations and timelines for candidates and electorate contained in these governance documents[1][2][3]. Due to circumstances of timing, PTL and TC elections for the coming cycle will run concurrently; deadlines for their nomination and voting activities are synchronized but will still use separate ballots. Please note, if only one candidate is nominated as PTL for a project team during the PTL nomination period, that candidate will win by acclaim, and there will be no poll. There will only be a poll if there is more than one candidate stepping forward for a project team's PTL position. Similarly, there will only be a TC poll if there are more than 5 candidates stepping forward the available TC positions. All members of the community are encouraged to confirm their email address as described at: https://governance.openstack.org/election/#electorate All candidates and prospective voters need to make sure they have reestablished their individual memberships in the Open Infrastructure Foundation https://openinfra.org/a/renew-membership (if this URL redirects you to your profile page, your membership is already renewed and nothing more is required), otherwise their nominations won't be verified and ballots will not be sent. There will be further announcements posted to the mailing list as action is required from the electorate or candidates. This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you wish to discuss in private please email any of the election officials[4] so that we may address your concerns. Thank you, [1] https://governance.openstack.org/tc/reference/charter.html [2] https://governance.openstack.org/tc/reference/role-of-the-tc.html [3] https://docs.openstack.org/project-team-guide/ptl.html [4] https://governance.openstack.org/election/#election-officials

1 0

[ironic] A first-class physical location API?
by Jay Faulkner 04 Feb '26

04 Feb '26

Something I've seen come up in a few discussions over the last couple of cycles is the need for Ironic to contain more useful information about the physical world. It's made me wonder if there's an opportunity to add bigger support for physical characteristics/locations? I'm thinking metadata like: - Datacenter the server is in - Computer room (or other DC subdivision) - Row - Rack - Slot # - Physical cabling (e.g. what switches you might be connected to and how) Do other folks see this need? I'm trying to tease out if there's something here or not, so just curious about use cases and what people think. -Jay

4 5

[tc][ptls] Streamlining the OpenStack User Survey
by Allison Price 03 Feb '26

03 Feb '26

Hi everyone, Today in the OpenStack TC meeting, I shared the intention of streamlining the OpenStack User Survey[1] in an effort to increase participation while still preserving the valuable insights we get from the responses. As a next step, I wanted to share an etherpad[2] with some context on what we are trying to achieve with this process as well as some pointed questions to help guide us as we make changes to improve the survey. If you have taken or reviewed the results of the OpenStack User Survey, please share your insights. This is an incredibly valuable tool and I want to ensure that any changes that we make are intentional and can help support the upstream community. I know everyone is in the middle of 2026.1 Gazpacho work, so we have some time. If possible, I would like to have as much input as possible in the etherpad by April 15 so we can then use the upcoming virtual PTG[3] to go through the responses and make a plan. Then, we can implement the changes in August 2026 for the next version of the survey. If you have any questions or would like to ensure you’re a part of this process, please let me know. I will send reminders as we get closer to the PTG. Thanks, Allison [1] https://www.openstack.org/user-survey [2] https://etherpad.opendev.org/p/OpenStack-User-Survey-Streamlining [3] https://openinfra.org/ptg

1 0

[neutron] IPv6 DVR for OVN - Seeking feedback on patch review prospects
by Maximilian Stinsky-Damke 03 Feb '26

03 Feb '26

Hello, I'm reaching out about the IPv6 DVR feature for OVN (bug #1998609: https://bugs.launchpad.net/neutron/+bug/1998609) and the associated patch (https://review.opendev.org/c/openstack/neutron/+/867513) As noted in the bug comments, Roberto Bartzen Acosta maintained this patch across multiple release cycles, but it hasn't received reviews from core maintainers and is currently blocked by merge conflicts. Roberto mentioned that the feature hasn't been getting traction despite the work put in. This feature would enable distributed routing for IPv6 GUA addresses in OVN deployments, similar to how IPv4 FIPs work with DVR today. The spec was approved and merged (https://review.opendev.org/c/openstack/neutron-specs/+/867979) indicating community interest. Before I invest time rebasing the patch and resolving merge conflicts, I'd like to understand: 1. Are there technical or architectural concerns that have prevented review? 2. Is there a reason this hasn't been prioritized, or is it a matter of reviewer availability? 3. Would core maintainers be willing to review if the patch is rebased and updated? I'm happy to do the rebase work, but I'd prefer not to spend time on something that won't be merged. Any guidance on the status and viability of this feature would be appreciated. Thanks, Max

2 5

OVN issues
by engineer2024 03 Feb '26

03 Feb '26

HI, I am trying to setup an extport host to act as host for an sriov vm IP. Set it up using ovs-vsctl set Open_vSwitch . external_ids:ovn-cms-options=enable-chassis-as-extport-host But when a vm is created with this sriov port, it is not able to reach the metadata service at 169.254.169.254. Inside the vm vm:~# ip r 10.1.0.0/24 dev ens5 proto kernel scope link src 10.1.0.20 169.254.169.254 via 10.1.0.12 dev ens5 proto dhcp src 10.36.160.60 metric 100 On the node marked as the extport host for this vm's ip, its ovn-controller log shows --------- 2026-01-29T11:52:26.922Z|00069|binding|INFO|Setting lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf up in Southbound 2026-01-29T11:52:27.849Z|00070|binding|INFO|Releasing lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf from this chassis (sb_readonly=0) 2026-01-29T11:52:27.851Z|00071|binding|INFO|Setting lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf down in Southbound 2026-01-29T11:52:28.480Z|00072|binding|INFO|Claiming lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf for this chassis. 2026-01-29T11:52:28.480Z|00073|binding|INFO|a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf: Claiming fa:16:3e:f3:82:f9 10.1.0.20 2026-01-29T11:52:28.482Z|00074|binding|INFO|Setting lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf up in Southbound 2026-01-29T11:52:29.486Z|00075|binding|INFO|Releasing lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf from this chassis (sb_readonly=0) 2026-01-29T11:52:29.489Z|00076|binding|INFO|Setting lport a7c94e2b-58f1-4a6d-8c73-1d0e6f92b4cf down in Southbound ------------ It is fluctuating intermittently and not stable. Why is this flapping ? Also the metadata proxy is running fine on the extport host ip netns exec ovnmeta-7d9a4c21-1e6f-4f2b-9a84-3c8e1b7d62f0 telnet 169.254.169.254 80 Trying 169.254.169.254... Connected to 169.254.169.254. # ip netns exec ovnmeta-7d9a4c21-1e6f-4f2b-9a84-3c8e1b7d62f0 ss -ln | grep 80 tcp LISTEN 0 1024 169.254.169.254:80 <http://169.254.169.254/> 0.0.0.0:* # ps -ef | grep ovn-meta root 408634 1 9 11:52 ? 00:02:45 neutron-ovn-metadata-agent (/openstack/venvs/neutron-29.2.3/bin/python3 /openstack/venvs/neutron-29.2.3/bin/neutron-ovn-metadata-agent --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_ovn_metadata_agent.ini) root 408673 1 0 11:52 ? 00:00:00 haproxy -f /var/lib/neutron/ovn-metadata-proxy/7d9a4c21-1e6f-4f2b-9a84-3c8e1b7d62f0.conf root 421770 388277 0 12:21 pts/12 00:00:00 grep --color=auto ovn-meta

2 1

[manila] Removal of the "manila" CLI
by Carlos Silva 03 Feb '26

03 Feb '26

Hello everyone, Following up on our deprecation of the manila shell client, we are officially announcing its removal in the 2026.1 Gazpacho release [1]. The legacy manila shell was first deprecated in the OpenStack Zed release. Since then, we have achieved full feature parity with our OpenStackClient (OSC) plugin. Moving forward, Manila will exclusively support the "openstack share" command set. No new features have been added to the legacy "manila" client since its deprecation, and it did not support recent API microversions. The manila executable will no longer be installed or supported. All management and provisioning tasks must be performed using the openstack CLI (e.g., openstack share create instead of manila create). If you are still using the "manila" command in your automation, CI/CD pipelines, or daily workflows, please migrate to the openstack CLI immediately. We appreciate your cooperation as we move toward a more maintainable OpenStack CLI experience. Regards, carloss [1] https://review.opendev.org/q/topic:%22bp/openstack-client-support%22+(statu…

1 0

[manila] Removal of the long deprecated "v1" API
by Carlos Silva 03 Feb '26

03 Feb '26

Hello everyone, After being deprecated for nearly a decade, the Manila V1 API is officially being removed from the codebase [1]. This effort will be completed in the 2026.1 Gazpacho release. Since the introduction of the Microversioned V2 API, V1 has been deprecated. However, to reduce technical debt and streamline our maintenance efforts, we are finally decommissioning it. In the Gazpacho release, the /v1 endpoint will cease to exist. While we sunset this API, please note that the /v2 API at micro-version 2.0 is identical to the /v1 API. Action Required: If you have legacy scripts or integrations still pointing to the V1 endpoint (which we do not expect at this point), please update them to use the V2 API immediately. [1] https://review.opendev.org/q/hashtag:%22remove-manila-api-v1%22+(status:ope… Regards, carloss

1 0

[neutron] Bug Deputy Report Jan 26 - Feb 01
by Yatin Karel 03 Feb '26

03 Feb '26

Hi Neutrinos, Below is the bug deputy report for last week:- Critical ====== - https://bugs.launchpad.net/neutron/+bug/2139271 - [FT] Failing test ``test_gateway_chassis_balanced_scheduling_multiple_gw_networks`` Fixed by Rodolfo High ==== - https://bugs.launchpad.net/neutron/+bug/2139143 - [OVN] ``_sync_ha_chassis_group`` fails if the current HCG has more than ``MAX_CHASSIS_IN_HA_GROUP`` HA_Chassis registers Assigned to Rodolfo Medium ====== - https://bugs.launchpad.net/neutron/+bug/2139586 - [whitebox-neutron-tempest-plugin] Metadata tests should be execute with OVN agent too Assigned to Rodolfo - https://bugs.launchpad.net/neutron/+bug/2139063 - Ensure no RPC clients are instantiated if ``rpc_workers=0`` Assigned to Rodolfo - https://bugs.launchpad.net/neutron/+bug/2139581 - Updating router state fails due to NoneType error Assigned to William Tripp Low === - https://bugs.launchpad.net/neutron/+bug/2139416 [doc] Document what changes are needed when changing supported Python version Unassigned Incomplete - https://bugs.launchpad.net/neutron/+bug/2139583 - neutron-openvswitch-agent native driver: Permanent flow loss after OVS restart due to unhandled 'unknown dpid' during rpc_loop Looks valid but requested more details -- Thanks and Regards Yatin Karel

1 0

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

02 Feb '26

Hello Stackers, We're 8 weeks away from the date of the coordinated release of OpenStack 2026.1 "Gazpacho" [1]. Next week is the feature freeze for OpenStack's Common Library projects ("oslo"), and this includes python-openstackclient and python-openstacksdk for this release. It's also the deadline for PTLs and DPL liaisons to propose additional names as contributors to OpenStack [2]. Please take this opportunity to credit folks who have been contributing to project maintenance without having any merged changes via Gerrit. Recording these individuals' contributions as "Active Contributors" acknowledges their effort and allows them to vote in the upcoming elections. Speaking of elections, the nomination period for TC and PTL elections begins this week. If you intend to contest these elections, please do submit your candidacy [3]. In the past week, the OpenStack Technical Committee began updating projects that followed the "Distributed Leadership" model during the 2026.1 "Gazpacho" release cycle. The release management team has opted to govern itself using the distributed leadership model and has retained the liaisons. The Watcher project has decided to move to the PTL model, and its PTL will be elected in the upcoming elections. We're awaiting decisions from the Ironic, Requirements, Freezer, and Oslo projects. Please review the open governance patches to help these teams make appropriate governance decisions. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee was hosted on January 27th, 2026 in OFTC's #openstack-tc IRC channel [4]. We focused our attention toward the 2026.2 Election cycle, which is fast approaching. Nominations open on February 4 and run through February 18 [5]; since our election officials are spread a bit thin this time, several TC members who aren't seeking re-election stepped up to help attest nomination patches. We’ve decided to retarget the MariaDB/MySQL Character Set community goal. While it’s a vital piece of technical debt to address, we’re looking to define and commit to this in the 2026.2 cycle to ensure the rollout is realistic and implementable across the projects. We had a robust discussion regarding updating the Technical Vision [6] and how it intersects with the Foundation’s "Next Level in 2026" initiatives [7]. The goal here isn't just to produce a static document, but to use the vision as a tool to refocus the "What is OpenStack?" question, helping us stay consistent as we also define how to evolve the vision. We also touched upon the retirement of some inactive projects in the 2026.2 "Hibiscus" cycle [8]. We hope to make practical decisions in the interest of conserving the community's energy and focusing on paying down technical debt such as eventlet removal. The next meeting of the OpenStack TC is on Tuesday, February 3rd, 2026. It'll be at 1700 UTC in OFTC's #openstack-tc channel. Please find the agenda on the meeting's wiki [9]. This week we're looking to discuss improvements to the User Survey, revival of Cyborg, and begin planning our presence at the PTG in April. I hope you're able to participate. === Governance Proposals === ==== Merged ==== - Remove rbd-iscsi-client from release management | https://review.opendev.org/c/openstack/governance/+/972316 - Remove barbican-ui from release management | https://review.opendev.org/c/openstack/governance/+/972315 - Update mission statement for kolla project | https://review.opendev.org/c/openstack/governance/+/974421 - Reset the DPL model for watcher project | https://review.opendev.org/c/openstack/governance/+/974926 ==== Open For Review ==== - Move FIPS Compliance goal back to proposed | https://review.opendev.org/c/openstack/governance/+/969145 - Reset the DPL model for Oslo project | https://review.opendev.org/c/openstack/governance/+/974929 - Reset the DPL model for Freezer project | https://review.opendev.org/c/openstack/governance/+/974931 - Reset the DPL model for requirements project | https://review.opendev.org/c/openstack/governance/+/974927 - Reset the DPL model for Ironic project | https://review.opendev.org/c/openstack/governance/+/974930 - Revert "Revive os_monasca" | https://review.opendev.org/c/openstack/governance/+/974775 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] Nominate "Extra ACs": https://releases.openstack.org/gazpacho/schedule.html#extra-ac-freeze [3] Be a candidate this election: https://governance.openstack.org/election/#how-to-submit-a-candidacy [4] TC Meeting IRC Log, Jan 27 2026: https://meetings.opendev.org/meetings/tc/2026/tc.2026-01-27-17.00.html [5] 2026.2 Elections: https://governance.openstack.org/election/ [6] Vision for OpenStack Clouds: https://governance.openstack.org/tc/reference/technical-vision.html [7] "Next Level in 2026": https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [8] Inactive Projects: https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [9] TC Meeting Agenda, Feb 03 2026: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

Digital Sovereignty WG Kickoff Summary + Recording + Next Steps
by Kendall Nelson 02 Feb '26

02 Feb '26

Hello Everyone! Thank you to those that were able to attend our first meeting of the Digital Sovereignty Working Group! We had excellent representation from many different countries and organizations. Lots of good perspective and ideas were shared and I am eager to get started! As promised, here is the recording for those that were not able to attend: https://zoom.us/rec/share/QLyhngha_pgXEc2736oPEdDGWz_UI8IZLbHbJGyDWLv7nt4es… And here is the etherpad where we took notes, but will also continue to use going forward for meeting agendas and general working group coordination: https://etherpad.opendev.org/p/Digital-Sovereignty-WG If you watch the recording, please feel free to add your name to the attendees list in the etherpad, just make an additional note that you watched the recording. Everyone is encouraged to add to the notes and content in the etherpad whether they attended the meeting live or watched the recording. The goal is to capture as much participation as possible. Digital sovereignty is a very important topic with an ever developing list of accompanying legislation and we need everyone's perspective! Now, while there wasn't much in the way of immediate todo's, the one request that I have is that folks fill out this poll so that we can select a meeting time <https://beta.framadate.org/polls/5f355daf8e4329e1cd52> for the next one (during the first week of February). Responses to this poll are allowed until January 28th. -Kendall

1 2

[nova] gate fix for broken nova-alt-configurations
by Ghanshyam Maan 01 Feb '26

01 Feb '26

Hi All, WIth the recent change in tempest, nova-alt-configurations is broken for the rbac policy access. I proposed the fix, please avoid recheck until fix is merged - https://review.opendev.org/c/openstack/tempest/+/975356 - gmaan

1 0