September 2025 - openstack-discuss

[openstack][kolla-ansible]about group node config overwrite
by Nguyễn Hữu Khôi 30 Oct '25

30 Oct '25

Hello Koller. I want to ask if we can overwrite config for a group of nodes. For example, compute01 >> compute10 will have the same nova configuration compute11 >> compute20 will have the same nova configuration. It will be very nice if we support this way. Thank you. Regards Nguyen Huu Khoi

4 7

[all][dev][ops][tc] Bridging the gap between community and contributing orgs
by Jeremy Stanley 25 Oct '25

25 Oct '25

The tl;dr on this is that I'm opening a broad community discussion on how we can, collectively through improved communication, better bring together our established contributors with casual and prospective contributors who struggle to find successful patterns of contribution, so that we might all support each other in order to benefit OpenStack as a whole. Read on for details... OpenStack's TC has requested that foundation staff, when in conversation with representatives of member organizations, encourage participation in the project and collect feedback on any related challenges those organizations encounter in their attempts to do so. In order to better understand the feedback and brainstorm achievable recommendations for the broader community[*], Community Managers on the foundation staff started to work with a small focus group of established contributors with a solid understanding of what successful patterns of contribution look like. It also came to light that established contributors experience many of the same sorts of challenges, even more so if they don't have the luxury of focusing full-time upstream, and so success often comes down to knowing how to effectively navigate those challenges. The community's goal with this exercise is to improve everyone's experience, and your help is needed to do that! The most common themes reported by those struggling to contribute are not related to tooling or workflow confusion, but instead seem to come down to basic communication challenges. Ideas so far to address these gaps include: * Review bandwidth - Ensure contributors and companies understand the importance and benefits of code review - Incentivize and credit meaningful "+1" reviews more - Understand that the volume of changes and limited reviewer bandwidth often means proposals aren't reviewed quickly (or at all), and their proponents may need some additional tenacity and engagement with the team to get their work noticed - Utilize "review dashboards" as a way to find stale changes which have fallen through the cracks * Review strategy and etiquette - Be clear about the meaning of votes on changes, especially negative ones, and set explicit timelines for things like "procedural -2" or WIP blocks when their approval needs to be delayed - Focus on comments and requests that affect whether or not the change can be merged after the fixes are submitted, rather than requesting trivial adjustments to an unsuitable change which has more fundamental problems - Reciprocate with reviews of changes from new reviewers you see leaving insubstantial reviews, demonstrating to them what deeper and more meaningful reviewing looks like * Mentoring newcomers - Established contributors with sufficient bandwidth can help mentoring newcomers, potential core reviewers and new leaders - Mentoring can happen as part of internship programs as well as by helping newcomers determined to become active contributors; both ways should be embraced and utilized What challenges are you facing? And, how would you improve them? Two weeks from now, we'll have a forum session at the OpenInfra Summit Asia in Suwon[**] where our community can refine these possible approaches and integrate others, as well as bring attention to them and promote their application. I've also proposed a similar forum session for OpenInfra Days North America in Indianapolis a month after that, where we can hopefully continue this conversation. The goal for this multi-stage effort is to improve the contribution experience for established participants, casual contributors and newcomers alike. While it's easy to jump to blaming in these situations, it will be far more productive if we can focus on the challenges and experiences that we would each like to remove or improve for ourselves and others in our community. As we find ways together to improve our efficiency, we can reduce the load on all contributors and lower the barriers for people to join and participate. [*] https://etherpad.opendev.org/p/r.2205024e55689bccb82c20c960853cb5 [**] https://2024.openinfraasia.org/a/schedule#view=calendar&title=Bridging%20th… -- Jeremy Stanley

2 12

[ptg][nova][ironic][cinder]cross-project sessions
by Iury Gregory 24 Oct '25

24 Oct '25

Hello nova and cinder folks, In the preparation for the upcoming PTG, we have some topics that we would like to discuss - *[ironic][nova] *Graphical Console follow-up https://etherpad.opendev.org/p/ironic-ptg-2026.1#L137 - *[ironic][nova][cinder] *NVMe over TCP https://etherpad.opendev.org/p/ironic-ptg-2026.1#L75 Next week we will be booking some time slots for ironic, feel free to reachout to us on #openstack-ironic with the time slots that would work for all teams. Best regards, -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic Core* *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

2 3

[PTG][ironic][neutron] cross-project session
by Iury Gregory 24 Oct '25

24 Oct '25

Hello neutron folks, In the preparation for the upcoming PTG, we would like to have a cross-project section to discuss about the VXLAN attachments [1] , we can book a slot that would work for the people that are interested in the topic. Next week we will be booking some time slots for ironic, feel free to reachout to us on #openstack-ironic with the time slots that would work for the neutron team. [1] https://etherpad.opendev.org/p/ironic-ptg-2026.1#L97 Best regards, -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic Core* *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

2 3

[openstack][octavia]Resize a Load Balancer
by Nguyễn Hữu Khôi 23 Oct '25

23 Oct '25

Hello. I see that patch https://review.opendev.org/c/openstack/octavia/+/890215 Could I ask why we cannot merge it? Nguyen Huu Khoi

3 5

[oslo][messaging] Container fix of QManager breaks it for containers
by Dmitriy Rabotyagov 22 Oct '25

22 Oct '25

Hey folks, I wanted to raise attention to a relatively old issue, which has had a patch around since January [1]. Basically a regression [2] was introduced and backported to 2024.1 as part of an attempt to fix QManager execution in containers. However, it does not account for the possibility of os.getpgrp() returning 0 in some edge cases, which makes, for instance, impossible to sync database for Nova during upgrades, if QManager is used. Thus I'm asking to kindly review the [1] as it appears to be a blocker for some upgrades involving affected versions of oslo.messaging. I have not spotted this patch right away, so I proposed an alternative [3], but I'm happy to abandon it in favor of [1]. Thanks in advance for upcoming reviews :) [1] https://review.opendev.org/c/openstack/oslo.messaging/+/939540 [2] https://review.opendev.org/c/openstack/oslo.messaging/+/928034 [3] https://review.opendev.org/c/openstack/oslo.messaging/+/958528

2 3

[Octavia][Load Balancer][2023.1] Amphora Fails Health Check – “No Route to Host” & Timeout Errors
by Thamanna Farhath 15 Oct '25

15 Oct '25

Hi OpenStack Community, I am currently facing an issue with the Load Balancer (Octavia) service in my OpenStack deployment and would appreciate your guidance or suggestions on how to troubleshoot and resolve it. Environment Details: OpenStack Version: 2023.1 (Antelope) Operating System: Ubuntu 22.04 Octavia Backend: Amphora Network Type: VXLAN Deployment Tool: Kolla Ansible Issue Summary: After creating a Load Balancer, the Amphora instance is successfully launched. However, approximately 18 minutes later, the Load Balancer transitions to an ERROR state. Error Observed: octavia.common.exceptions.ComputeWaitTimeoutException: Waiting for compute id a222527f-8336-4fb1-8e9e-0e3ac6e8d580 to go active timeout. octavia.amphorae.driver_exceptions.exceptions.AmpConnectionRetry: Could not connect to amphora, exception caught: HTTPSConnectionPool(host='192.168.200.247', port=9443): Max retries exceeded with url: // (Caused by NewConnectionError: Failed to establish a new connection: [Errno 113] No route to host) What I’ve Tried: Created a VXLAN-based internal network: openstack subnet create --network octavia-mgmt-net --subnet-range 192.168.200.0/24 octavia-mgmt-subnet openstack router create octavia-router openstack router add subnet octavia-router octavia-mgmt-subnet openstack router set octavia-router --external-gateway <public-network-id> Manually configured OVS interface: ovs-vsctl add-port br-int octavia-mgmt -- set interface octavia-mgmt type=internal ip addr add 192.168.200.1/24 dev octavia-mgmt ip link set octavia-mgmt up Security groups are open (allowing all ingress and egress). Verified OVS bridge setup – interface appears correctly on br-int. Behavior Noticed: Amphora instance gets created but fails to communicate with the controller after a while,so health checks fails. The controller cannot reach the Amphora management IP (192.168.200.x). Logs show heartbeat/connection issues (No route to host, timeouts). Request for Help: I would appreciate any of the following: Suggestions to verify if the management network is properly routed from controller to Amphora. Best practices for setting up the Octavia management network using VXLAN. Troubleshooting steps for verifying health manager connectivity to Amphora. Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

3 2

[Ceph Tracing] Limited Jaeger traces for OSD, no MON/MGR/RGW
by Thamanna Farhath 14 Oct '25

14 Oct '25

Hello openstack Community, I am using Ceph as the backend storage for OpenStack and deployed it via ceph-ansible.I enabled Jaeger tracing on Ceph cluster using: - Global Ceph config: ceph config set global jaeger_tracing_enable true - Jaeger Docker all-in-one docker run -d --name jaeger -e COLLECTOR_ZIPKIN_HOST_PORT=:9411 -e COLLECTOR_OTLP_ENABLED=true --network host -p 6799:6799/udp -p 6832:6832/udp -p 5778:5778 -p 16686:16686 -p 4317:4317-p 4318:4318 -p 14250:14250 -p 14268:14268 -p 14269:14269 -p 9411:9411 jaegertracing/all-in-one:1.27 --processor.jaeger-compact.server-host-port=6799 Issue: - Only OSD traces appear with limitation traces(`enqueue_op`, `op-request-created`) - No traces from MON, MGR, or RGW Questions: 1. Is this the correct process for enabling tracing? 2. How can I capture traces for MON, MGR, RGW? 3. How can I see all OSD operations? Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

2 3

[neutron] oslo.messaging and port notifications broadcast
by Thomas Goirand 09 Oct '25

09 Oct '25

Hi, Is it possible, with oslo.messaging, to have 3 daemons to get the Neutron port.{create,update,delete}.end notification events? I tried hard, but no mater how I do it, only one of my 3 daemons get the message. I'm about to add forwarding feature to the other 2 when one receives an event. Is there a better way? Cheers, Thomas Goirand (zigo)

5 12

[ptl][venus][tc] Need a PTL volunteer for OpenStack Venus project team
by Goutham Pacha Ravi 08 Oct '25

08 Oct '25

Hello Stackers, We're missing a Project Team Lead (PTL) for the OpenStack Venus project team for the "2026.1" (Gazpacho) release cycle. If you're interested, please let us know by proposing a PTL appointment (e.g. [1]). Thanks, Goutham Pacha Ravi (gouthamr) [1] https://review.opendev.org/c/openstack/governance/+/899781

1 2

[ptl][vitrage][tc] Need a PTL volunteer for OpenStack Vitrage project team
by Goutham Pacha Ravi 08 Oct '25

08 Oct '25

Hello Stackers, We're missing a Project Team Lead (PTL) for the OpenStack Vitrage project team for the "2026.1" (Gazpacho) release cycle. If you're interested, please let us know by proposing a PTL appointment (e.g. [1]). Thanks, Goutham Pacha Ravi (gouthamr) [1] https://review.opendev.org/c/openstack/governance/+/882139

1 2

[ptl][tc] OpenStack 2025.2 Flamingo OpenInfra Live
by Allison Price 02 Oct '25

02 Oct '25

Hi everyone, As we get closer to next week’s release, I wanted to reach out about doing an OpenInfra Live episode about OpenStack 2025.2 ‘Flamingo.” If you are a PTL or TC member who would like to present project highlights, please let me know. The episode will air next Thursday, October 2 at 1400 UTC. If you are unfamiliar, you can check out the Epoxy version here: https://www.youtube.com/watch?v=qX2-8oyFVPk Cheers, Allison

5 7

East-West and the compute VM flows come to a centralized gateway for security audit
by Andy Zhou 02 Oct '25

02 Oct '25

Hello Everyone, Any advice about configure of Openstack or OVN/OVS, to implement a centralized gateway of all the flows of VMs for flow audit? Since the default type is distributed mode for the East-West flow, I want to know if we can change to a centralized one? Thank you! Best regards, Andy Zhou

2 2

I can not get user list with project in openstack version epoxy
by cheung 01 Oct '25

01 Oct '25

Dears: I can get user list with project in openstack version caracal. # openstack project list -f value 7fb2be327b4c4f9e83db04a4b5cb922b service c1bcb532eca44aadabb028b1ee715412 admin de4012f880e7408f9fb21b67930c21ac project_it # openstack user list -f value 84b39214b13148d68bf88242aa6abdf9 admin 62f7113645c24199a9946cd16911ca64 glance b21da7173fe3400f91d3eb73f392474d nova 95a6ff7b9bba42f9aadf3b07a0811330 placement 4ac268a8e75b4a4288f067e28ad14425 neutron 46fa578d54624e06ae2e0b3761a67de7 cinder 1c1646579b5042a6bb463e8f46b7762f test001 57689f8310e744889dce33d6b32f4524 test002 # openstack user list -f value --project project_it 1c1646579b5042a6bb463e8f46b7762f test001 57689f8310e744889dce33d6b32f4524 test002 # openstack user list -f value --project service 4ac268a8e75b4a4288f067e28ad14425 neutron 46fa578d54624e06ae2e0b3761a67de7 cinder b21da7173fe3400f91d3eb73f392474d nova 62f7113645c24199a9946cd16911ca64 glance 95a6ff7b9bba42f9aadf3b07a0811330 placement # dpkg -l| grep keyston ii keystone 2:25.0.0-0ubuntu1 all OpenStack identity service - Daemons ii keystone-common 2:25.0.0-0ubuntu1 all OpenStack identity service - Common files ii python3-keystone 2:25.0.0-0ubuntu1 all OpenStack identity service - Python 3 library ii python3-keystoneauth1 5.6.0-0ubuntu1.1 all authentication library for OpenStack Identity - Python 3.x ii python3-keystoneclient 1:5.4.0-0ubuntu1 all client library for the OpenStack Keystone API - Python 3.x ii python3-keystonemiddleware 10.6.0-0ubuntu1 all Middleware for OpenStack Identity (Keystone) - Python 3.x But I can not get user list in epoxy version. # openstack project list -f value 0087125cb3564da39a5e87dc61aece78 project_it 8b6a848d2d7841118567f1dad2eeb9f5 admin dcaa69462fd3447ca75133a8ce4b95c3 service # openstack user list -f value 27bd419eb7bc4da58f9e246232a12720 placement 7c5a457f461440e5a24a368f827ecafc admin 846cca4cb4394d1ab4e8d95dffb63ce2 glance 92122f012abb4db38a0d3ca287c04122 nova ad039b4d1f4f4c42a59e69e56eef4f16 neutron ebde13fec7584f5180becb88afa0e1c7 cinder f4cf0b16f52e407d994e2aa729936580 test002 f9ee38a0a4cb412dbd293a83b5b32dc5 test001 # openstack user list -f value --project project_it Either group or user should be specified # openstack user list -f value --project service Either group or user should be specified What do I miss? I need to read which one document? 本電子郵件及其所有附件所含之資訊均屬機密，僅供指定之收件人使用，未經寄件人同意不得揭露、複製或散布本電子郵件。若您並非指定之收件人，請勿使用、保存或揭露本電子郵件之任何部分，並請立即通知寄件人並完全刪除本電子郵件。網路通訊可能含有病毒，收件人應自行確認本郵件是否安全，若因此造成損害，寄件人恕不負責。 The information contained in this communication and attachment is confidential and is intended only for the use of the recipient to which this communication is addressed. Any disclosure, copying or distribution of this communication without the sender's consents is strictly prohibited. If you are not the intended recipient, please notify the sender and delete this communication entirely without using, retaining, or disclosing any of its contents. Internet communications cannot be guaranteed to be virus-free. The recipient is responsible for ensuring that this communication is virus free and the sender accepts no liability for any damages caused by virus transmitted by this communication.

3 4

Using slave_connection in keystone for a read-only local database node
by Tyler Wilson 01 Oct '25

01 Oct '25

Hello All, I'm trying to get keystone to respect my slave_connection configuration to use a local database node in my galera cluster. I have this set currently; connection = mysql+pymysql://keystone:$PASSWORD@$DB_PRIMARY_WRITE_IP/keystone slave_connection = mysql+pymysql://keystone:$PASSWORD@$DB_LOCAL_READ_IP/keystone However whenever I have this configured I still am getting queries sent to the $DB_PRIMARY_WRITE_IP for even simple things like 'openstack user list'. Is there some other configuration I need to set for this to go to the read DB node? I have query logging enabled on the mariadb side to confirm where the requests are going. For troubleshooting I changed them both to the local DB node IP, and it can indeed process the sql requests fine. Operating System: Ubuntu 24.04 Package Version: 2:25.0.0-0ubuntu1 Thanks for any assistance!

2 1

Debian packages for Flamingo are available and validated
by Thomas Goirand 30 Sep '25

30 Sep '25

Hi, I am finished packaging Flamingo, at least for all artifacts that were released already. I was able to run tempest on it, and all went well. I uploaded all to Debian Unstable already minor a few packages (like Ironic, that is having issues coping with pysnmp 7, and mistral that is stuck on one of its unit tests: I'll investigate both soon). Packages are available through the usual channel. To get the osbpo.debian.net backport repository for Trixie, do: apt-get install extrepo extrep enable openstack_flamingo apt-get update Note that osbpo is now updated automatically on all git push based on event, rather than a cron job, so it's kind of instant now. So there's no reason to use the http://<debian-suite>-<openstack-release.debian.net repositories anymore (these are now only useful for me, internally, to build backport packages with Jenkins). Also, the deb-status page is also event driven, and updated each time a new package is updated. Please see: https://osbpo.debian.net/deb-status/ In there, you will see that I also took the time to update all past OpenStack release to the latest point release for all deliverables. Please report bugs through the usual channel: https://www.debian.org/Bugs/Reporting I'll package final versions as they come, though changes are expected to be minimal (if any change at all), as for every OpenStack release. Cheers, Thomas Goirand (zigo)

1 0

[openstack] about libvirt exporter
by Nguyễn Hữu Khôi 30 Sep '25

30 Sep '25

Hello. I see that this exporter looks like it collects a lot of information such as projectname, username or flavor of metrics but it looks not popular. It could help us build a very useful dashboard. https://github.com/zhangjianweibj/prometheus-libvirt-exporter I just want to understand some thoughts. Nguyen Huu Khoi

3 3

how to spare resource for evacuation
by Jiatong Shen 30 Sep '25

30 Sep '25

Hello experts, I would like to ask if there is a way to reserve some resources (CPU and Memory) in advance and later use them in case one compute node crashes. For example, vSphere implemetens Cluster Resources Percentage Admission Control [1] and could reserve resources beforehand. Thank you very much for the help. -- Best Regards, Jiatong Shen [1] https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/vsphere-…

2 2

[i18n] Current Weblate Migration Status
by Seongsoo Cho 30 Sep '25

30 Sep '25

Hello i18n team, OpenStack's current translation platform(translation.openstack.org) is based on Zanata, which is no longer maintained. To ensure a sustainable translation workflow, the i18n team has been migrating from Zanata to Weblate. This work officially started following the CMU Summer semester mentoring shared by Kendall Nelson in May (link), and has since been moving forward in collaboration with the Korea User Group and mentees participating in the government-sponsored Open Source Contribution Academy program. 1. Migration progress Migration scope: - Download translated .po files from Zanata and upload them to Weblate - The same language set configured in Zanata is also applied in Weblate. Branches: - Currently, only the master branch is being migrated. - We are exploring ways to support stable branches in the future. Migration Contents: - At this stage, the migration targets strings inside source code and release notes. - We are in the process of expanding this to include documentation as well. We started with Horizon and its plugins, and the following projects have already been successfully migrated to Weblate: • cloudkitty-dashboard • designate-dashboard • freezer-web-ui • heat-dashboard • horizon • ironic-ui • magnum-ui • manila-ui • networking-bgpvpn • neutron-fwaas-dashboard • neutron-vpnaas-dashboard • octavia-dashboard • trove-dashboard • zaqar-ui • zun-ui 2. New Zuul jobs for Weblate To replicate the existing Zanata-based Zuul workflow, we are adding new Weblate jobs. • Patch: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/921878 We plan to reuse the translation-jobs-master-only Zuul templates and update the following playbooks to run both Zanata and Weblate tasks: • https://opendev.org/openstack/project-config/src/branch/master/playbooks/tr… • https://opendev.org/openstack/project-config/src/branch/master/playbooks/tr… • Patch: https://review.opendev.org/c/openstack/project-config/+/961499 3. Migration scripts Although they are one-off scripts, we are adding them to the i18n repository to document how we migrated from Zanata to Weblate. • Language sync tool: https://review.opendev.org/c/openstack/i18n/+/961371 • Zanata-to-Weblate migration tool: https://review.opendev.org/c/openstack/i18n/+/961075 4. Next steps for migration We have implemented everything needed to replace the Zanata-based jobs with Weblate. Once the Zuul job patches are merged, we will verify the upstream pipeline. Our goal is to migrate all projects from Zanata to Weblate by October. After verifying the pipeline, we plan to shut down Zanata. 5. Future plans Beyond this migration, we plan to expand translation targets — including OpenStack governance documents and the docs/ directories of many projects — to provide broader translation opportunities. Anyone interested in contributing is warmly welcome to join us in the #openstack-i18n IRC channel and say hello! Thanks, Best Regards Seongsoo Cho -- Seongsoo Cho OpenStack Korea User Group / Community Leader IRC #seongsoocho

3 4

[nova][cpu] Question about cpu_policy=dedicated with thread_policy=isolate in Victoria
by Aleksandar Cerepnalkovski 30 Sep '25

30 Sep '25

Hi all, What I'm trying to do is isolate vCPUs on separate physical cores where pair siblings will be reserved / not used by any other VM nor by this VM as well. Of course it is about SMT/HT enabled hosts. So by using a combination of extra spec on flavor (cpu_policy=dedicated , plus thread_policy=isolate), i'm always receiving errors ( no host available) . I'm using the Victoria OpenStack release. I've found (also playing with AI tools) that this combination is tricky (buggy) in Victoria and might not work and it might always fail. Actually what this combination is introduced for ? 1. If is it for what i meant ( forcing SMT enabled host to behave like non-SMT host, for some number of cores not all) then why is it not working ? 2. If not, what is the purpose of this combination ? Thanks, BR Aleksandar

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.2/R+0)
by Goutham Pacha Ravi 30 Sep '25

30 Sep '25

Hello Stackers, It's release week [1]! We've pulled out a lot of stops to get the 32nd release of OpenStack packed with exciting improvements [2]. Project teams have released their final RCs for all deliverables following the cycle-with-rc release model in preparation for the coordinated release on October 1st, 2025. Work has begun on the 2026.1 "Gazpacho" release [3]. This next one is a SLURP release—alongside major feature work, the community is actively prioritizing paying down technical debt, most of which has been identified as Community Goals [4]. In the next few weeks, cycle-trailing projects will work on supporting the 2025.2 "Flamingo" release. They will join the rest of the community in a week of design discussions at the OpenInfra Project Teams Gathering, scheduled for October 27–31st, 2025. If you're looking to seed or participate in a discussion here, please add your topics to the many discussion Etherpads that have been created for the event [5]. In the past week, the OpenStack Technical Committee was re-formed with three returning (frickler, bauzas, and cardoe) and one new member (tonyb). We're looking to fill roles such as TC chair, vice-chair, and liaisons to various project teams, including the OpenStack VMT, this week. The retirement of the "shade" client library was approved; functionality provided by this library has long been available as a part of openstacksdk. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee occurred on September 23rd, 2025 [6]. The meeting began by acknowledging the recently concluded TC elections, congratulating the elected members, and thanking the election officials for their work. We discussed the status of "leaderless" projects—Venus, Vitrage, and OpenStack Charms. For OpenStack Charms, Felipe Reyes (freyes) submitted a patch to appoint himself as PTL. For Venus and Vitrage, the committee decided to gather more data for a thorough discussion next week. The group noted low activity for Venus and maintenance activity for Vitrage, though its core-team list is significantly outdated and requires cleanup. The discussion also touched on the completed action item of vendoring the ply library into yaql, which sparked a lengthy debate on the implications for downstream package maintainers and distributions, with the consensus being to keep the change but acknowledge the concerns. The meeting wrapped up with a brief note on the broken CI for the Skyline project and attempts to contact the core maintainers whose time has been stretched thin. The next meeting of the OpenStack TC is today, September 30th, 2025. The meeting will be hosted on OFTC's #openstack-tc channel. Please find the meeting's agenda and other details on the wiki page [7]. I hope you'll be able to join us there! I'd like to note that any community member is welcome to edit this wiki page at any time to seed a new topic of discussion. === Governance Proposals === ==== Merged ==== - Add gouthamr's nomination for 2026.1 TC chair | https://review.opendev.org/c/openstack/governance/+/962049 - Fix small mistake with month in subject resolution | https://review.opendev.org/c/openstack/governance/+/962512 - Retire shade | https://review.opendev.org/c/openstack/governance/+/962197 - Add TC/PTL results from 2026.1 election | https://review.opendev.org/c/openstack/governance/+/961598 ==== Open For Review ==== - Appoint Felipe Reyes as PTL for OpenStack Charms | https://review.opendev.org/c/openstack/governance/+/962121 - Retire Monasca project | https://review.opendev.org/c/openstack/governance/+/953671 - Extend Monasca's inactive state | https://review.opendev.org/c/openstack/governance/+/959392 - Retire metalsmith project from bare metal program | https://review.opendev.org/c/openstack/governance/+/958297 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 === Upcoming Events === - 2025-10-01: OpenStack 2026.1 "Flamingo" release day - 2025-10-03: OpenStack's Birthday Meetup, Austin: https://www.meetup.com/openinfra-austin/events/310508680 - 2025-10-17: OpenInfra Summit, Paris-Saclay: https://summit2025.openinfra.org/ - 2025-10-27: OpenInfra PTG: https://openinfra.org/ptg/ - 2025-10-04: OpenInfra Board meeting: https://board.openinfra.org/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) [1] 2025.2 "Flamingo" Release Schedule: https://releases.openstack.org/flamingo/schedule.html [2] 2025.2 "Flamingo" Release highlights: https://releases.openstack.org/flamingo/highlights.html [3] 2026.1 "Gazpacho" Release Schedule: https://releases.openstack.org/gazpacho/schedule.html [4] OpenStack-wide Goals: https://governance.openstack.org/tc/goals/selected/index.html [5] Gazpacho PTG Etherpads: https://ptg.opendev.org/etherpads.html [6] TC Meeting IRC Log, Sep 23rd, 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-09-23-17.00.html [7] TC Meeting Agenda, Sep 30th, 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[ironic] Cancelling October 13th, 20th, 27th meetings.
by Julia Kreger 30 Sep '25

30 Sep '25

Greetings everyone, We're at the end of the release cycle and we will soon have a summit[0] *and* the PTG later in October. As such, the Ironic team discussed upcoming meetings during our weekly meeting[1] and reached the consensus to cancel the meetings for October 13th, 20th, and 27th. The 13th and 20th for proximity to Open Infra Summit, and the 27th because of the PTG[2] during which the team will likely be meeting the entire week. If you have any questions, please let us know! -Julia, on behalf of the Ironic project. [0] :https://summit2025.openinfra.org/ [1]: https://meetings.opendev.org/meetings/ironic/2025/ironic.2025-09-29-15.03.l… [2]: https://etherpad.opendev.org/p/ironic-ptg-2026.1

1 0

Need information on services
by engineer2024 29 Sep '25

29 Sep '25

Hi, Are there any existing projects in OpenStack equivalent to lambda in aws, which provides function-as-a service model ?

2 2

[openstack][nova]qemu system wont release memory
by Nguyễn Hữu Khôi 29 Sep '25

29 Sep '25

Hello. I have an OpenStack instance that was using 14GB out of 16GB of memory. Later, when it was using only 4GB, I checked the QEMU process on the compute node, and it was still consuming 14GB, this means memory isn't released when usage decreases. Do we have solutions for this? I use Ubuntu 24.04 instances. Nguyen Huu Khoi

2 4

[Neutron][operators] LinuxBridge to OVN Outreach
by Daniel Failing 29 Sep '25

29 Sep '25

Hi all, Following on the good session we had last time discussing migrating out of LinuxBridge between operators, it was proposed to meet again in June. To find a good time slot, please respond to the following survey: https://newdle.cern.ch/newdle/TtbH8Dbv For reference, the notes from last meeting: https://etherpad.opendev.org/p/neutron-lb-ovn-migration Best, Daniel Failing CERN Cloud Infrastructure

2 3

[neutron] Bug deputy report for week 39 of 2025 (September 21st)
by Miguel Lavalle 29 Sep '25

29 Sep '25

I was the Neutron bug deputy last week. Following is a brief summary of the reported bugs: High bugs -------------- https://bugs.launchpad.net/neutron/+bug/2125478 [OVN] External ports scheduler (using HA_Chassis_Group) should consider the physical network mappings. Assignee Rodolfo Alonso. https://bugs.launchpad.net/neutron/+bug/2125500 Metadata port fixed IPs missing from port. It needs an owner. Medium ----------- https://bugs.launchpad.net/neutron/+bug/2125553 [OVN] Collocate the external ports in the same chassis as the gateway port. Assignee Rodolfo Alonso. Proposed fix https://review.opendev.org/c/openstack/neutron/+/962155 https://bugs.launchpad.net/neutron/+bug/2125569 [OVN] The method to sync the HA_Chassis_Group should always update the "ignore_chassis" variable. Assignee Rodolfo Alonso. Proposed fix https://review.opendev.org/c/openstack/neutron/+/962191 https://bugs.launchpad.net/neutron/+bug/2125715 OVN DHCPv6 support for Option 59. Assignee Harald Jensas. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/962317 Need further refinement -------------------------------- https://bugs.launchpad.net/neutron/+bug/2125573 Octavia LB FIP reachability broken when VRRP failover happens https://bugs.launchpad.net/neutron/+bug/2125482 Subsequent BGP speaker scheduled onto dragent does not work -- Miguel Lavalle He/Him/His Principal Software Engineer - OpenStack Networking mlavalle(a)redhat.com M: +1 (713) 859-0591

1 0

ovpn-dco on RHEL10 based distribution
by William Muriithi 29 Sep '25

29 Sep '25

Hello, I have a openvpn server on RHEL10 and I would like to use ovpn-dco on it. Currently, I don't have a working kernel on it. 2025-09-24 10:27:17 us=861227 Note: Kernel support for ovpn-dco missing, disabling data channel offload. This is the only working binaries. openvpn-2.7_beta1-1.el10_0.alma_altarch.x86_64_v2 openvpn-auth-oauth2-1.26.0-1.x86_64 [root@openvpn-lab ~]# If I install openvpn-2.6, the openvpn server wouldn't start because of this error. symbol lookup error: /usr/sbin/openvpn: undefined symbol: EVP_MD_CTX_get_size_ex, version OPENSSL_3.4.0. The kernel module seem ok as the system at least boot. Its just that openvpn don't work after the system is up. So, only way seem to figure out how to get openvpn 2.7 module booting on RHEL10 Kallsyms_lookup_name+0x4/0xd0 kernel BUG at arch/x86/kernel/cet.c:102! Oops: invalid opcode: 0000 [#1] PREMPT SMP NOPTI Tainted: [0]=OOT_MODULE, [E]=UNSIGNED_MODULE This is how I installed the dco that is breaking the boot process. https://community.openvpn.net/Pages/OpenVPN%20software%20repos OpenVPN software repos – community wiki<https://community.openvpn.net/Pages/OpenVPN%20software%20repos> Introduction This page contains instructions for using OpenVPN project's own software repositories. For OpenVPN 3 Linux, see the dedicated OpenVPN 3 Linux page. The OpenVPN project provides the latest OpenVPN releases (and development snapshots) as packages for major Linux distributions. This allow you to use more up-to-date version of OpenVPN than what is typically available in your ... community.openvpn.net yum copr enable @OpenVPN/openvpn-beta yum install kmod-ovpn That is, after that, the system wouldn't boot. Have anyone found a way to run dco on RHEL10. This is a openVPN server, so I didn't bother trying openVPN 3 Any pointer would be appreaciated. Regards, William

2 1

skyline patch merging, release and backports
by Doug Goldstein 28 Sep '25

28 Sep '25

Hello, It appears that skyline, both skyline-console and skyline-apiserver, have been broken from a test standpoint for a bit. Additionally the last patch from not one of the core members that has been merged was June 12th, which is also the last time a core member has commented on a patch not from the core members. There has been a recent uptick in contributors coming from another organization and I would like to help see their contributions land. Some of these are fixes so that the tests actually pass as well as fixes for other bugs and new features. There have also been requests for backports to 2025.1. What do we need to get this work to start landing and make sure this project stays healthy? fix for skyline-console tests: https://review.opendev.org/c/openstack/skyline-console/+/961092 fix for one of the two failing skyline-apiserver tests: https://review.opendev.org/c/openstack/skyline-console/+/961092 open skyline-apiserver changes: https://review.opendev.org/q/project:openstack/skyline-apiserver+status:open open skyline-console changes: https://review.opendev.org/q/project:openstack/skyline-console+status:open Thanks. — Doug

4 7

[openstack-ansible]Add Banner on openstack login page
by keshav bareja 27 Sep '25

27 Sep '25

Hi Team We need to add a banner or notification with a custom text on the openstack login page. Is there any way to do that ? openstack-ansible Carcal release 2024.1 Horizon 29.2.2 Regards Keshav Bareja

3 2

[ops][largescale-sig] Refactoring Ops-related activities - a discussion at the PTG
by Thierry Carrez 26 Sep '25

26 Sep '25

Hi everyone, We have several groups working in the OpenStack community to propose activities and content that are relevant to OpenStack operators: - The Ops meetup[1] group, currently producing Ops Radio Hour - The Large Scale SIG[2], producing the Scaling Journey documentation and the Large Scale OpenStack webinars - The Public Cloud SIG and the Scientific SIG, which focus on specific usage cases - Probably others that I miss... All of those groups overlap, and struggle with gathering enough volunteers to drive them forward. The fragmentation also hurts their discoverability for OpenStack operators out there, who are hungry to learn about the challenges of operating OpenStack and would like to hear more from the teams that do that successfully. I'd like to propose an open discussion at the PTG next month on how to refactor our ops-facing activities under a single, visible, and active banner. I propose we take a PTG meeting slot on Friday, October 31, at 16utc to discuss that with all interested volunteers. Thoughts, comments? -- Thierry Carrez (ttx)

2 1

[release] Release countdown for week R+0
by Thierry Carrez 26 Sep '25

26 Sep '25

Development Focus ----------------- We will be releasing the coordinated OpenStack 2025.2 "Flamingo" release next week, on October 1st, 2025. Thanks to everyone involved in the 2025.2 "Flamingo" cycle! We are now in pre-release freeze, so no new deliverable will be created until final release, unless a release-critical regression is spotted. Otherwise, teams attending the PTG should start to plan what they will be discussing there, by creating and filling team etherpads. You can access the list of PTG etherpads at: http://ptg.openstack.org/etherpads.html General Information ------------------- On release day, the release team will produce final versions of deliverables following the cycle-with-rc release model, by re-tagging the commit used for the last RC. A patch doing just that will be proposed. PTLs and release liaisons should watch for that final release patch from the release team. While not required, we would appreciate having an ack from each team before we approve it on the 1st, so that their approval is included in the metadata that goes onto the signed tag. Upcoming Deadlines & Dates -------------------------- Final 2025.2 "Flamingo" release: October 1st, 2025 OpenInfra Summit Europe: October 17th-19th, 2025 OpenStack PTG (virtual): October 27th-31st, 2025 -- Thierry Carrez (ttx)

1 0

For Information
by Suraj Silwal 26 Sep '25

26 Sep '25

I am just participating, I need get to go , please help me how I set up and contribute in openstack.

2 1

[openstack-ansible][ussuri] moving openstack deployment node to other host
by Danish Khan 25 Sep '25

25 Sep '25

Dear Team, Our controller1 node which was also openstack deployment node somehow crashed and is not accessible now. I am trying to make controller3 as new deployment node. Below is the step which I am planning to follow. I have backup of (openstack-ansible, openstack_deploy and ansible directory of controller1 ): 1. Place /opt/openstack-ansible directory from controller1 to controller3 2. copy /etc/openstack_deploy directory from controller1 to controller3 3. copy /etc/ansible/ directory from controller1 to controller3 4. run bootstrap on controller3 5. test if openstack-ansible has picked same clusters and inventory. Can someone please suggest if this is correct approach or if I am missing something. Regard, Danish

2 1

[kolla] [swift] Seeking reviews for reinstating Swift support for 2025.2
by Amir Hossein Ahmadi 25 Sep '25

25 Sep '25

Hello Kolla and OpenStack community, A few months ago, Swift support was removed from the Kolla project due to several challenges, including the need for role modernization, the lack of dedicated maintainership, and persistent CI failures. Following that, I volunteered to take on this effort. Over the last few months, I have been working to address these issues and am happy to report significant progress: - *Modernized Roles:* The Swift roles have been fully updated to align with the latest Kolla and Kolla-Ansible development standards. - *Reliable CI:* The associated Zuul jobs are now consistently green, with all tests successfully validated. - *Maintainership:* I have stepped up to maintain the Swift service within Kolla, ensuring its long-term health and stability. A considerable amount of effort has been invested to ensure this implementation is robust and maintainable for the community. With the *2025.2 release deadline just four weeks away*, the final and most critical step is to get these patches reviewed and merged. Your feedback and reviews are crucial to landing this work in time for the release. Reinstating Swift support would be a valuable addition for many operators. Any time you can spare to look over the patches would be greatly appreciated. You can find the main patch series here: https://review.opendev.org/q/topic:%22dev-swift-modernization%22 Thank you for your consideration and for all your contributions to the OpenStack community. Best regards, Amir Hossein (IRC: amir58118)

5 5

[largescale-sig] Next meeting: September 23, 14utc
by Thierry Carrez 24 Sep '25

24 Sep '25

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC at 14UTC. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250923T14 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

2 3

Upgrade Caracal --> Epoxy obstacles
by Eugen Block 24 Sep '25

24 Sep '25

Good morning, I just wanted to share some of our experience from this week when we upgraded our production cloud from Caracal to Epoxy (and also Ubuntu 22.04 --> 24.04). It wasn't as easy as previous upgrades, there were a couple of obstacles on the way. # RabbitMQ The main issue was rabbitmq, I'd say. Since the rabbitmq version was 3.9 on Jammy, we had to get to 3.12 for Noble. I had tried a lot of things in my test environment, in the end I decided to reduce the number of rabbitmq hosts to one, upgraded it with podman from 3.9 to 3.10 to 3.11 to enable the feature flags required for 3.12 (all still under Jammy). Then I could upgrade the OS to Noble so the package based rabbitmq-server would start successfully. # Database The recent thread about older password hashes (https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack…) was helpful, we set the same passwords for those system users that came up in the MySQL query, and we didn't notice any issue. But there were two issues we had to deal with regarding the database: During nova-manage db sync we got these errors: 2025-09-22 14:08:19 2 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), fou nd type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB'). 2025-09-22 14:08:19 2 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255). This had not popped up during my tests, but our production database is around 10 years old when we started with our OpenStack journey, my test environment is quite new. What fixed it was: mysql_upgrade check-if-upgrade-is-needed Then there's another thing I have to fully grasp yet, but we now have a ".local" directory in /var/lib/mysql: find /var/lib/mysql/.local/share/containers/storage/ /var/lib/mysql/.local/share/containers/storage/ /var/lib/mysql/.local/share/containers/storage/libpod /var/lib/mysql/.local/share/containers/storage/db.sql Which mysql_upgrade didn't like. I assume that podman created that, but I'm not sure why (I only created a rabbitmq pod). Anyway, I removed that directory so I could proceed with the db sync commands to complete the upgrade process. In my test cloud I removed podman, then restarted galera and the directory is gone, so that's what I'm gonna do in the production as well. # opentack-client Then there are these messages during every openstack command: Could not load 'message_list': module 'zaqarclient.queues.v2.cli' has no attribute 'OldListMessages' Could not load 'message_post': module 'zaqarclient.queues.v2.cli' has no attribute 'OldPostMessages' I'll need to check if they impact any of our scripts, we don't use zaqar, but removing that package would also remove heat, so that won't be possible. # nova-compute: I waited for version 19.2.1 of librbd1 to be released, otherwise nova-compute would fail: qemu-block-extra : Depends: librbd1 (>= 19.2.1-0ubuntu0.24.04.1) but 19.2.0-0ubuntu0.24.04.2 is to be installed # neutron-metadata-agent There's a bug for functioning agents showing as dead, applying the mentioned patches fixes it: https://bugs.launchpad.net/neutron/+bug/2112492 # Pacemaker We use pacemaker for high availability and during the dist-upgrade I had to run 'apt --fix broken', then remove resource-agents and resource-agents-base to get through the dist-upgrade, then install pacemaker and crmsh again afterwards. Not sure if anyone will read this far, but I wanted to get that off my chest. ;-) So obviously, most of the issues weren't really OpenStack issues, but I wanted to share this experience anyway. If you read this far, thanks! ;-) Regards, Eugen

3 2

[kolla] Weekly meeting cancelled today (24th Sep 2025)
by Michał Nasiadka 24 Sep '25

24 Sep '25

Hello, Apologies for bad timing, but the weekly meeting is cancelled today due to lack of key participants. See you next week! Michal

1 0

[ops][largescale-sig][scientific-sig] Ops Radio Hour on September 26, 2025
by Ildiko Vancsa 24 Sep '25

24 Sep '25

Hi OpenStack community, I'm reaching out to you with a friendly reminder that the next OpenStack Ops Radio Hour[1] is scheduled to happen on __September 26th, 2025 at 1300UTC.__ The call series is a casual setting for operators, engineers, and contributors to come together, share knowledge, and collaborate on the complexities of managing and deploying OpenStack environments. Topics the next gathering will dive into: - (SWIFT) Compliance processes If you have further topics you would like to dive into during the call, please add them to this etherpad: https://etherpad.opendev.org/p/openstack_ops_radiohour A few reminders: - The group on the call agreed to try out Matrix as a chat platform for more synchronous communication outside calls + You can access the Matrix room here: https://matrix.to/#/#openstack-ops:opendev.org<https://matrix.to/#/%23openstack-ops:opendev.org> + Further details are here: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… - If you would like to read and catch up on notes from previous calls, you can find them in this etherpad: https://etherpad.opendev.org/p/openstack_ops_radiohour See you on the call on September 26th! Bets Regards, Ildikó [1] https://wiki.openstack.org/wiki/Operations/Meetups

1 1

[watcher] watcher and affinity policy
by Nguyễn Hữu Khôi 24 Sep '25

24 Sep '25

Hi, Would you like to correct me if I understand that watcher will not consider server groups when it does jobs? If I am right, do we have any solutions to this problem? Thank you. Regards Nguyen Huu Khoi

3 3

[tc][all] OpenInfra Summit 2025 Open Source Pavilion Opportunity
by Clark Boylan 24 Sep '25

24 Sep '25

The OpenInfra Summit 2025 will host an Open Source Pavilion booth space where open source projects can book an hour or two to showcase their work, engage with attendees, and share updates on their latest developments at the Summit. If you are interested in taking advantage of this opportunity for your project please fill out this form [0] and the event planners will get back to you with scheduling details. This seems like a good opportunity for both the broader OpenStack community to engage with attendees, and also for specific OpenStack projects, working groups, and SIGs. Feel free to followup with any questions you might have here on this thread, and I'll do my best to get answers. I suspect that you can also get the process started by filling out the form, and the organizers can followup with you to answer questions as well. [0] https://openinfrafoundation.formstack.com/forms/open_source_pavillion Clark

2 1

[designate] DNS records stuck in PENDING state but records created succesfully
by Jadon Naas 24 Sep '25

24 Sep '25

Hello! I am using Designate on 2023.2 with a PowerDNS backend. I have a recordset with three A records created through Designate. The A records are stuck in "PENDING" state with action "CREATE" or "UPDATE". The records were successfully created in PowerDNS, and changes are pushed to PowerDNS. However, the record status never finishes updating. Deleting and recreating the recordset results in the same situation. I do not see any notable errors in the logs for Designate or for PowerDNS. I have checked that the Desigate configuration for the nameservers and for the targets match the correct IP addresses for my PowerDNS server and for my Designate service hosts. Would folks have any suggestions for what I could do to determine what is preventing Designate from updating these records or to manually update the status of the records? Thank you! Jadon Naas

2 1

[publiccloud-sig] Public Cloud SIG meeting d.d. 23 September
by Kees Meijs | Nefos 24 Sep '25

24 Sep '25

Hello Stackers, Tomorrow (that's 23 September) the bi-weekly Public Cloud SIG meeting will be held again. The publicly available video meeting will be conducted from 07:00 hrs UTC (09:00 hrs CEST) and on 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 1

Compatebilty
by nahoms＠altacomputec.com 23 Sep '25

23 Sep '25

The customer currently uses 15 Dell PowerEdge R650 servers for their OpenStack private cloud and wants to expand. Is there any compatibility issue if we propose Lenovo servers along with the existing Dell ones?

2 1

[octavia] Creation of several master amps
by yardalgedal＠gmail.com 23 Sep '25

23 Sep '25

Hi all, we're using octavia of version zed and caught a case when it regularly creating 3 amphorae instead of 2. We have not had any amphorae for which of these LBs and I did failover for each of them: openstack loadbalancer amphora list --loadbalancer 70f98bfb-8045-4d4a-9729-d60b6e141dbf openstack loadbalancer failover 70f98bfb-8045-4d4a-9729-d60b6e141dbf openstack loadbalancer amphora list --loadbalancer 96223d34-6941-4bc5-881a-ddfd83070739 openstack loadbalancer failover 96223d34-6941-4bc5-881a-ddfd83070739 openstack loadbalancer amphora list --loadbalancer f9f859d0-2b31-449b-8723-700bb7f3f3f4 openstack loadbalancer failover f9f859d0-2b31-449b-8723-700bb7f3f3f4 then first backup amphorae was created pretty fast openstack loadbalancer amphora list --loadbalancer 70f98bfb-8045-4d4a-9729-d60b6e141dbf openstack loadbalancer amphora list --loadbalancer 96223d34-6941-4bc5-881a-ddfd83070739 openstack loadbalancer amphora list --loadbalancer f9f859d0-2b31-449b-8723-700bb7f3f3f4 +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | 3dfa43cd-2719-487e-8ba2-8a4aa0fe7301 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | ALLOCATED | BACKUP | 10.94.64.112 | 10.210.73.197 | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | b39472aa-04a0-42b8-8c09-4617ea1a0f33 | 96223d34-6941-4bc5-881a-ddfd83070739 | ALLOCATED | BACKUP | 10.94.64.232 | 10.210.64.32 | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ | 60af8e11-c6ad-45f0-8e07-1bcc4a477444 | f9f859d0-2b31-449b-8723-700bb7f3f3f4 | ALLOCATED | BACKUP | 10.94.64.74 | None | +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ but then it started to create 2x Master's for each (!) of them (we can talk about lags, but not in case of 3x): openstack loadbalancer amphora list --loadbalancer 70f98bfb-8045-4d4a-9729-d60b6e141dbf openstack loadbalancer amphora list --loadbalancer 96223d34-6941-4bc5-881a-ddfd83070739 openstack loadbalancer amphora list --loadbalancer f9f859d0-2b31-449b-8723-700bb7f3f3f4 +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | 3dfa43cd-2719-487e-8ba2-8a4aa0fe7301 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | ALLOCATED | BACKUP | 10.94.64.112 | 10.210.73.197 | | 3dd9bdb4-0dfe-4d77-b08f-02fbbffcd892 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | BOOTING | None | None | None | | ff6ec3de-6942-4978-9ea5-d793ff1fdbf8 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | BOOTING | None | None | None | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | b39472aa-04a0-42b8-8c09-4617ea1a0f33 | 96223d34-6941-4bc5-881a-ddfd83070739 | ALLOCATED | BACKUP | 10.94.64.232 | 10.210.64.32 | | 9909b300-d266-4344-b6fc-edc4af651485 | 96223d34-6941-4bc5-881a-ddfd83070739 | BOOTING | None | None | None | | cc123c55-2953-425e-867e-f4057483bb09 | 96223d34-6941-4bc5-881a-ddfd83070739 | BOOTING | None | None | None | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ | 60af8e11-c6ad-45f0-8e07-1bcc4a477444 | f9f859d0-2b31-449b-8723-700bb7f3f3f4 | ALLOCATED | BACKUP | 10.94.64.74 | None | +--------------------------------------+--------------------------------------+-----------+--------+---------------+-------+ as a result we started to have 3x Master's for them openstack loadbalancer amphora list --loadbalancer 70f98bfb-8045-4d4a-9729-d60b6e141dbf openstack loadbalancer amphora list --loadbalancer 96223d34-6941-4bc5-881a-ddfd83070739 openstack loadbalancer amphora list --loadbalancer f9f859d0-2b31-449b-8723-700bb7f3f3f4 +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | 3dfa43cd-2719-487e-8ba2-8a4aa0fe7301 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | ALLOCATED | BACKUP | 10.94.64.112 | 10.210.73.197 | | 3dd9bdb4-0dfe-4d77-b08f-02fbbffcd892 | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | ALLOCATED | MASTER | 10.94.64.56 | 10.210.73.197 | | 14e8acfe-8510-4629-a583-53ba88f91eca | 70f98bfb-8045-4d4a-9729-d60b6e141dbf | ALLOCATED | MASTER | 10.94.64.30 | 10.210.73.197 | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ | b39472aa-04a0-42b8-8c09-4617ea1a0f33 | 96223d34-6941-4bc5-881a-ddfd83070739 | ALLOCATED | BACKUP | 10.94.64.232 | 10.210.64.32 | | 9909b300-d266-4344-b6fc-edc4af651485 | 96223d34-6941-4bc5-881a-ddfd83070739 | ALLOCATED | MASTER | 10.94.64.151 | 10.210.64.32 | | 9d197234-6411-4069-8be3-a399cc1fbc3a | 96223d34-6941-4bc5-881a-ddfd83070739 | ALLOCATED | MASTER | 10.94.64.212 | 10.210.64.32 | +--------------------------------------+--------------------------------------+-----------+--------+---------------+--------------+ +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | id | loadbalancer_id | status | role | lb_network_ip | ha_ip | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ | 60af8e11-c6ad-45f0-8e07-1bcc4a477444 | f9f859d0-2b31-449b-8723-700bb7f3f3f4 | ALLOCATED | BACKUP | 10.94.64.74 | 10.211.193.63 | | d086f283-b9d8-4b23-a782-e0ace769e893 | f9f859d0-2b31-449b-8723-700bb7f3f3f4 | ALLOCATED | MASTER | 10.94.64.225 | 10.211.193.63 | | 8a90fc7c-eb0a-4635-8ece-7c4704c60f7a | f9f859d0-2b31-449b-8723-700bb7f3f3f4 | ALLOCATED | MASTER | 10.94.64.50 | 10.211.193.63 | +--------------------------------------+--------------------------------------+-----------+--------+---------------+---------------+ taskflow is enabled in our case, backend is redis can you suggest smth to check or maybe some updates were already done?

3 3

[all][tc] Retrospective for OpenStack Elections
by Goutham Pacha Ravi 23 Sep '25

23 Sep '25

Hello Stackers, The OpenStack Technical Committee would like to take a moment to reflect on the recently concluded elections [1][2]. Elections and renewal of governance are a cornerstone of our Open Community principle [3]. We firmly believe that well-governed projects are sustainable and successful. In the recent elections, we saw 78 electors cast their votes to elect members to the TC out of 173 eligible voters. Jeremy Stanley (fungi) is planning to follow up with some more detailed analysis, but I wanted to kick-start this thread to share a few insights and initiate a call-to-action. To be eligible to contest or vote in OpenStack elections, you must meet two criteria: - You must be an Active Contributor, which means you have had a change merged in the roughly one-year period prior to the elections. - You must be an "Individual Member" of the OpenInfra Foundation (not a "Community Member") at the time the electoral rolls are created. This date is published and typically occurs a few days before polling begins. For the recently concluded 2026.1 elections, we identified over 650 active contributors in the one-year timeframe. However, as you can see, the number of eligible voters and the number of actual voters were significantly smaller. We've identified a few key reasons for this: - Individual Membership Renewal: In the past few months, as the OIF has transitioned under the Linux Foundation, we asked all individual members to "renew" their memberships. OIF staff and OpenStack election officials noticed a drop in the electorate due to this new requirement. It's quite easy for an email seeking renewal to get lost in a crowded inbox. - Opt-in for Ballots: We host our elections with CIVS, a free and secure internet voting service. A ballot arrives via email when polling begins, but CIVS will not send you an email unless you have opted in. While we have tried to remind folks to enable these emails, they can still get "lost" in the noise. - Membership Type Confusion: Many of us may not realize that we need to be an "Individual" member of the OIF to participate in the governance process. I feel we need to do a better job of reminding people why this is needed, so they can make an informed choice about whether they'd like to impact the governance of OpenStack. Nearly 500 contributors are currently either "Community" members or have no affiliation with the OIF. We'd like to hear your thoughts and ideas on how we can improve in these areas (are there any more?). What can we do to ensure a wider and more engaged electorate in future elections? We believe that increasing participation is essential for the long-term health and success of the OpenStack community. Thank you, Goutham Pacha Ravi (gouthamr) OpenStack Technical Committee [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [2] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] https://opendev.org/openinfra/four-opens/src/branch/master/doc/source/openc….

2 1

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.2/R-1)
by Goutham Pacha Ravi 23 Sep '25

23 Sep '25

Hello Stackers, We're wrapping up work on the 2025.2 "Flamingo" release [1] within all projects that follow the "cycle-with-rc" release model [2]. The coordinated release is scheduled for October 1, 2025. You can follow the cycle highlights that Project Team Leads and liaisons have put together to get a preview of what this release brings [3]. In the past week, election officials posted results from the Combined TC/PTL elections for the 2026.1 release cycle [4][5]. I'm happy to welcome Tony Breeds (tonyb) and welcome back Doug Goldstein (cardoe), Dr. Jens Harbott (frickler), and Sylvain Bauza (bauzas) to the OpenStack Technical Committee. On behalf of the TC, I'd also like to congratulate the newly appointed PTLs of 34 project teams. This includes Arnaud Morin (amorin), who is leading the Mistral project as a first-time PTL, and Li Liu (liliueecg), who is returning to Cyborg as PTL after the Stein release. Thank you all for dedicating your time to fill these important roles. In the past week, the TC didn't merge any new governance changes; however, a few are currently undergoing community review. === Weekly Meeting === The TC held its weekly meeting on OFTC's #openstack-tc IRC channel on September 16, 2025 [6]. We discussed the community's participation in the election process [7] and are seeking input on how the process can be improved. It's possible that any changes we come up with would need buy-in from the OpenInfra Foundation's Board and staff. We followed up on the effort to standardize database character sets and collations across OpenStack projects [8]. The TC agreed that consistency would be beneficial for operators and supported the plan to make this a community goal. We'll follow up regarding the details. We touched on the status of "leaderless" projects, specifically Venus, OpenStack Charms, and Vitrage. If we find no PTL volunteers, the TC plans to follow up with the project teams and discuss options like retirement, finding liaisons and switch projects to a DPL governance model, or moving the projects to a Special Interest Group (SIG). We briefly discussed the upcoming PTG (Project Teams Gathering), with a suggestion to dedicate the first two days to cross-project discussions to encourage collaboration. The meeting concluded with a discussion about vendoring a BSD-3 licensed library, ply, into the yaql project, which the TC approved after confirming the license is compatible with OpenStack's Apache V2 license [9]. The next meeting of the OpenStack Technical Committee is on September 23, 2025. This meeting will be hosted on OFTC's #openstack-tc IRC channel and will begin at 1700 UTC. Please find the meeting's agenda on the wiki [10]. I hope you'll be able to join us there! === Governance Proposals === ==== Open For Review ==== - Add TC/PTL results from 2026.1 election | https://review.opendev.org/c/openstack/governance/+/961598 - Retire metalsmith project from bare metal program | https://review.opendev.org/c/openstack/governance/+/958297 - Retire Monasca project | https://review.opendev.org/c/openstack/governance/+/953671 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - Extend Monasca's inactive state | https://review.opendev.org/c/openstack/governance/+/959392 === Upcoming Events === - 2025-10-01: OpenStack 2026.1 "Flamingo" release day - 2025-10-03: OpenStack's Birthday Meetup, Austin: https://www.meetup.com/openinfra-austin/events/310508680 - 2025-10-17: OpenInfra Summit, Paris-Saclay: https://summit2025.openinfra.org/ - 2025-10-27: OpenInfra PTG: https://openinfra.org/ptg/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) [1] 2025.2 "Flamingo" Release Schedule: https://releases.openstack.org/flamingo/schedule.html [2] "cycle-with-rc" release model: https://releases.openstack.org/reference/release_models.html#cycle-with-rc [3] 2025.2 "Flamingo" Release highlights: https://releases.openstack.org/flamingo/highlights.html [4] 2026.1 TC election results: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [5] 2026.1 PTL election results: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [6] TC Meeting IRC Log, Sep 17th 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-09-16-17.00.html [7] 2026.1 Election Retrospective: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [8] Dealing with Mariadb/Mysql changes: https://etherpad.opendev.org/p/gazpacho-collations-charsets [9] Vendoring ply in OpenStack: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [10] TC Meeting Agenda, Sep 23rd 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[diversity] [outreachy] Call for mentors for Dec 2025 cohort
by Dmitry Tantsur 23 Sep '25

23 Sep '25

Hi folks! It's the Outreachy time of the year. Despite the enormous financial and organizational difficulties, the December cohort will start soon, and OpenStack is, as usual, a part of it. We're looking for mentors and their projects. Please submit your ideas to https://www.outreachy.org/communities/cfp/openstack/ by this Friday, Sep 26th. You can check my blog post https://owlet.today/posts/how-to-propose-the-best-project-for-outreachy/ on some tips. Note that, just like in the previous cycle, we'll only be able to fund one intern. I still hope we get a few project proposals for interns to choose from. Let me know if you have any questions! Dmitry on behalf on OpenStack community coordinators. P.S. Apologies for the late notice: it took us some time to confirm everything.

1 0

[neutron] bug deputy report for 2025w38
by Bence Romsics 22 Sep '25

22 Sep '25

Hi Team, We had the following new reports last week. Two of the High bugs are unassigned at the moment. High: * https://bugs.launchpad.net/neutron/+bug/2124252 [L3] A router with multiple GW ports fails when deleting the first one fixes proposed by Rodolfo: https://review.opendev.org/q/topic:bug/2124252 * https://bugs.launchpad.net/neutron/+bug/2124254 [L3] A router with multiple GW ports, if the first is deleted, the GW info is empty unassigned * https://bugs.launchpad.net/neutron/+bug/2124269 Can't bind an HA router_gateway port to chassis unassigned, could be related to the migration to HA Chassis Group RFEs: * https://bugs.launchpad.net/neutron/+bug/2123836 [RFE] Set a local TXT record in the DHCP agent/dnsmasq * https://bugs.launchpad.net/neutron/+bug/2124215 [RFE] Implement more graceful handling of dhcp_lease_duration reduction Opinion: * https://bugs.launchpad.net/neutron/+bug/2123848 [ovn-octavia-provider] Octavia LB not reachable with custom firewall appliance According to Froyo this should be discussed with OVN cores first. Invalid: * https://bugs.launchpad.net/neutron/+bug/2124259 [ovn] Direct routing (non NAT) does not work between VLAN and Geneve networks Problematic backport of WIP patches. * https://bugs.launchpad.net/neutron/+bug/2125034 During live-migration nova-conductor report 'No valid host was found' due to duplicated port bindings This looks like a nova bug, so I routed it to them. Cheers, Bence

1 0

[kolla][kolla-ansible] Python dependency handling in custom Ansible module without toolbox
by sarah.kh09＠gmail.com 22 Sep '25

22 Sep '25

Hi everyone, I'm developing a new Ansible module for one of the kolla-ansible roles, and it depends on a Python package that needs to be installed via pip on the target nodes. I understand that Kolla Ansible generally avoids installing Python packages directly on hosts, and prefers handling such dependencies through the kolla_toolbox container. However, in my case: - Deploying a sidecar container isn't feasible within our current architecture - Delegating execution to localhost or kolla_toolbox would introduce complexity that we’d rather avoid Given these considerations, I'm looking for alternative ways to handle this dependency while staying aligned with Kolla's principles of reproducibility and container isolation. Has anyone faced a similar situation or found a clean workaround? Is using kolla-toolbox the only standard and recommended approach in such cases? Thanks a lot for your help and feedback!

2 2

[nova] Nova API call duration increases after upgrading to Caracal
by Chang Xue 22 Sep '25

22 Sep '25

Hello, we recently upgraded from Bobcat to Caracal. After upgrading, an interesting increment of duration of nova api call is observed. It's involved to multiple API calls, e.g. os-query-sets, /v2.1/servers/detail, etc. And it seems to be accumulated, meaning whenever nova-api is restarted, the duration seems to be fairly fast, giving response within like 80, 90 ms. As it keeps running for like up to 10 days, the duration increases to over 500 ms. I noticed that Caracal is using UnifiedLimitsDriver instead of DbQuotaDriver. I tried to change nova.conf to use DbQuotaDriver but it seems not working well with reducing the duration. I understand that calling to Keystone and Placement (and likely other external APIs) could result to longer duration, but pretty confused why it shows up as accumulated. Wondering if anyone else in Openstack community noticed the similar issue, thanks!

6 14

[aodh][ceilometer] how create alarms with prometheus ceilometer backend
by Nguyễn Hữu Khôi 22 Sep '25

22 Sep '25

Hello. I try to set up alarm such as: openstack alarm create --type prometheus --type prometheus --name memory_high_alarm --query 'memory_usage{resource_id="21d0792e-2d01-4df9-958a-d9018d13207f"}' --threshold 10 I use ceilometer with prometheus backend but when it shows: +---------------------------+------------------------------------------------------------------+ | Field | Value | +---------------------------+------------------------------------------------------------------+ | alarm_id | cb7b8d07-0af1-4771-92c8-1a4c2ce4d1d1 | | name | memory_high_alarm | | description | prometheus alarm rule | | enabled | True | | ok_actions | [] | | alarm_actions | [] | | insufficient_data_actions | [] | | repeat_actions | False | | type | prometheus | | time_constraints | [] | | project_id | 31ef81adc8ad406e9e91e3eb8776c959 | | user_id | 2e7a252719434d93ae0d270c8753294d | | timestamp | 2025-09-18T14:10:50.467568 | | state | *insufficient data * | | state_timestamp | 2025-09-18T14:10:50.467568 | | state_reason | Not evaluated yet | | severity | low | | evaluate_timestamp | 2025-09-18T14:10:50.485384 | | comparison_operator | eq | | threshold | 10.0 | | query | memory_usage{resource_id="21d0792e-2d01-4df9-958a-d9018d13207f"} | +---------------------------+------------------------------------------------------------------+ and in aodh logs: 2025-09-18 21:20:02.442 1079 INFO aodh.evaluator [-] initiating evaluation cycle on 1 alarms 2025-09-18 21:20:02.442 1079 WARNING aodh.evaluator [-] Skipping alarm cb7b8d07-0af1-4771-92c8-1a4c2ce4d1d1, unsupported type: prometheus I am using openstack 2025.1 I would like to get some guides on this, Many thanks. Nguyen Huu Khoi

2 6

[aodh]how the evaluation process works
by Nguyễn Hữu Khôi 22 Sep '25

22 Sep '25

Hello, I would like to understand how the evaluation process works. For example, I have this rule: openstack alarm create --name memory_use_test \ --type gnocchi_resources_threshold \ --metric memory.usage \ --threshold 102 \ --comparison-operator gt \ --aggregation-method mean \ --granularity 60 \ --evaluation-periods 3 \ --resource-id dca36039-c603-422c-8366-f6ba4e9539c3 \ --resource-type instance Does this mean that when the alarm-evaluator service is running per a period, it will check the last 3 data points, each aggregated over 60 seconds? Thank you. Regards. Nguyen Huu Khoi

2 2

[ptl][charms][tc] Need a PTL volunteer for OpenStack Charms project team
by Goutham Pacha Ravi 21 Sep '25

21 Sep '25

Hello Stackers, We're missing a Project Team Lead (PTL) for the OpenStack Charms project team for the "2026.1" (Gazpacho) release cycle. If you're interested, please let us know by proposing a PTL appointment (e.g. [1]). Thanks, Goutham Pacha Ravi (gouthamr) [1] https://review.opendev.org/c/openstack/governance/+/943254

2 2

[release] Release countdown for week R-1, Sep 22 - 26
by Elõd Illés 20 Sep '25

20 Sep '25

Development Focus ----------------- We are on the final mile of the 2025.2 "Flamingo" development cycle! Remember that the 2025.2 "Flamingo" final release will include the latest release candidate (for cycle-with-rc deliverables) or the latest intermediary release (for cycle-with-intermediary deliverables) available. September 26th, 2025 is the deadline for final 2025.2 "Flamingo" release candidates as well as any last cycle-with-intermediary deliverables. We will then enter a quiet period until we tag the final release on October 1st, 2025. Teams should be prioritizing fixing release-critical bugs, before that deadline. Otherwise it's time to start planning the 2026.1 "Gazpacho" development cycle, including discussing Forum and PTG sessions content, in preparation of OpenInfra Summit Europe (Paris-Saclay, France; October 17th-19th, 2025) and virtual OpenStack PTG (October 27th-31st, 2025). Actions ------- Watch for any translation patches coming through on the stable/2025.2 branch and merge them quickly. If you discover a release-critical issue, please make sure to fix it on the master branch first, then backport the bugfix to the stable/2025.2 branch before triggering a new release. Please drop by #openstack-release with any questions or concerns about the upcoming release ! Upcoming Deadlines & Dates -------------------------- Final 2025.2 "Flamingo" release: October 1st, 2025 OpenInfra Summit Europe: October 17th-19th, 2025 OpenStack PTG (virtual): October 27th-31st, 2025 Előd Illés irc: elodilles @ #openstack-release

1 0

[neutron] VPN service/router stays PENDING_CREATE - 2024.2 Dalmatian
by Shubham Yadav 19 Sep '25

19 Sep '25

Hello OpenStack Community, I'm working with OpenStack VPNaaS (using strongSwan as the backend driver) and have a question about tunnel configuration capabilities. Current Setup: OpenStack VPNaaS with strongSwan driver (StrongSwanDriver) Single VPN Service (gateway) with multiple IPSec Site Connections Each connection targets different remote peers with distinct subnets Configuration Details: VPN Service: Connected to a single router Multiple IPSec Site Connections under the same VPN Service: Connection 1: To MY office (10.10.100.0/24) via peer 68.x.y.34 Connection 2: To Rackspace (172.24.60.0/22) via peer 184.n.p.53 Shared IKE and IPSec policies across connections Local endpoint groups covering multiple subnets (192.168.0.0/24, 10.43.0.0/16) Question: Is it supported/recommended to have multiple IPSec Site Connections under a single VPN Service? I understand this creates multiple tunnels from the same OpenStack router to different remote peers. Current Issue: One of my connections shows "PENDING_CREATE" status while the other is "ACTIVE". I'm trying to determine if this is: A configuration issue on my end A limitation of having multiple tunnels per VPN service A strongSwan-specific behavior in the OpenStack context Specific Questions: Does VPNaaS officially support multiple IPSec connections per VPN Service? Are there any known limitations or best practices when using multiple tunnels? Should each remote site have its own dedicated VPN Service instead? I've checked the documentation but couldn't find clear guidance on multi-tunnel scenarios. Any insights from the community would be greatly appreciated. Environment: OpenStack version: 2024.2 Dalmatian Neutron VPNaaS with strongSwan backend Kubernetes-deployed OpenStack (OpenStack-Helm) Waiting for your reply, Thank you for your time and assistance! Best regards, Shubham

1 0

[all][elections][ptl] 2026.1 Gazpacho: PTL Election Conclusion & Results
by Sławek Kapłoński 19 Sep '25

19 Sep '25

Hi, Thank you to the electorate, to all those who voted and to all candidates who put their name forward for Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability. Thank you to all those who make this process possible. Now for the results of the PTL election process, please join me in extending congratulations to the following PTLs: * Adjutant - Dale Smith (dalees) * Barbican - Mauricio Harley (mharley) * Blazar - Pierre Riteau (priteau) * Cinder - Jon Bernard (jbernard) * Cloudkitty - Rafael Weingartner () * Cyborg - Li Liu () * Designate - Omer Schwartz () * Glance - Cyril Roelandt () * Heat - Takashi Kajinami (tkajinam) * Horizon - Tatiana Ovchinnikova (tmazur) * Keystone - Artem Goncharov (gtema) * Kolla - Michal Nasiadka (mnasiadka) * Magnum - Dale Smith (dalees) * Manila - Carlos Silva (carloss) * Masakari - sam sue () * Mistral - Arnau Morin (amorin) * Neutron - Brian Haley (haleyb) * Nova - Rene Ribaud (Uggla) * Octavia - Michael Johnson (johnsom) * OpenStack Helm - Vladimir Kozhukalov (kozhukalov) * OpenStackAnsible - Dmitriy Rabotyagov (noonedeadpunk) * OpenStackSDK - Artem Goncharov (gtema) * Puppet OpenStack - Takashi Kajinami (tkajinam) * Quality Assurance - Ghanshyam Maan (gmaan) * Rally - Andrey Kurilin (andreykurilin) * Skyline - Wenxiang Wu (wu_wenxiang) * Storlets - Takashi Kajinami (tkajinam) * Sunbeam - Guillaume Boutry (gboutry) * Swift - Tim Burke (timburke) * Tacker - Yasufumi Ogawa (yasufum) * Telemetry - Matthias Runge (mrunge) * Trove - wu chunyang (wuchunyang) * Zaqar - Hao Wang (wanghao) * Zun - Hongbin Lu () Elections: * Horizon: https://civs1.civs.us/cgi-bin/results.pl?id=E_2cbcfa05fd0ec211 For remaining projects (without PTL candidates), TC will work on the appointment. Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all involved in the PTL election process, Slawek Kaplonski, on behalf of the OpenStack Technical Election Officials

2 1

PTG October 2025 Team List Announcement
by Kendall Nelson 19 Sep '25

19 Sep '25

Hello Everyone! The October 2025 Project Teams List is official! Projects + Teams - OpenInfra Project Teams - Kata Containers - StarlingX - - OpenStack - Services - Blazar - Cinder - CloudKitty - Ironic - Keystone - Kolla - Magnum - Manila - Neutron - Nova - Octavia - OpenStack Horizon - OpenStack-Ansible - Sunbeam - Swift - Telemetry - Other OpenStack Teams - Eventlet Removal - openstack-i18n - Release Management - Technical Committee If your team was planning to meet and isn’t in this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Soon I will be contacting moderators to sign up for time via the PTGBot[1] once it is configured to accept those reservations. As usual, feel free to let us know if you have any questions! Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://opendev.org/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: http://ptg.openinfra.org/ <http://ptg.openinfra.o/g>

1 0

[heat][mistral][tc] Status of ply
by Takashi Kajinami 19 Sep '25

19 Sep '25

Hi, As you might know, some of the OpenStack projects, heat and mistral, use yaql to support flexible user input. The yaql library has been tiny and stable, thanks to the ply[1] library which is the python-written implementation of lex and yacc . However, it was declared that no further release of ply is planned[2] and the author now suggests copying it into the project[3]. The old released version has been working so far, but I'm unsure if it could survive through recent drastic changes in python package tooling. Looking at the code, it seems all codes are tagged with BSD 3-clause license[3] though the repository lacks the LICENSE file. I guess that the easiest approach is to import the codes to somewhere within yaql (like yaql._ply) and use the imported codes, with a note explaining these codes are imported from ply. This follows the suggestion by the author, but I'd like to get some guidance from TC to make sure it won't break the whole license expectation. An alternative approach is to implement our own parser, though I'm not too sure if that's feasible at least from my PoV. If we want this approach, then we need actual volunteer for it who will immediately start working on it. If neither of the two options above work, we might end up removing yaql functionality completely from OpenStack. AFAIK the one in heat was added for TripleO which was already retired so the impact may be limited, while for mistral removal could have lager impact. Thank you, Takashi [1] https://github.com/dabeaz/ply [2] https://github.com/dabeaz/ply?tab=readme-ov-file#important-notice---october… [3] https://github.com/dabeaz/ply?tab=readme-ov-file#questions-and-answers [4] https://github.com/dabeaz/ply/blob/master/src/ply/lex.py#L10-L33 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

4 5

[horizon][ptg] Call for 2026.1 PTG Horizon topics
by Tatiana Ovchinnikova 19 Sep '25

19 Sep '25

Hello everyone, I have started to put together the etherpad [1] for the upcoming PTG to collect all Horizon related topics we wanted to discuss. Our usual session slots will stay, and if any other slot is needed, please feel free to suggest! [1] https://etherpad.opendev.org/p/horizon-gazpacho-ptg With kind regards, Tatiana

1 0

[all][elections][tc] 2026.1 Gazpacho Technical Committee Election Results
by Sławek Kapłoński 19 Sep '25

19 Sep '25

Hi, Please join me in congratulating the 4 newly elected members of the Technical Committe (TC). Sylvain Bauza (bauzas) Dr. Jens Harbott (frickler) Tony Breeds (tonyb) Doug Goldstein (cardoe) Full results: https://civs1.civs.us/cgi-bin/results.pl?id=E_6cede1084d4586eb Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all of the candidates, having a good group of candidates helps engage the community in our democratic process. Thank you to all who voted and who encouraged others to vote. We need to ensure your voice is heard. Thank you for another great round. Slawek Kaplonski, on behalf of the OpenStack Technical Election Officials

2 1

[openstack-helm] K8s cluster broken after reboot
by Viswanath Ediga 19 Sep '25

19 Sep '25

Hello All, I am trying openstack-helm for the fist time. I could deploy the kubernetes cluster using deploy-env <https://opendev.org/openstack/openstack-helm/src/branch/master/roles/deploy…> role in a multinode test environment. But after the reboot of controlplane node, cluster seems to be brokent Kubectl is giving below error *kubectl get pods -AError from server (Forbidden): pods is forbidden: User "kubernetes-admin" cannot list resource "pods" in API group "" at the cluster scope* Any help is appreciated Regards, Kasi Viswanath

1 0

[neutron] L3 routing using VPP
by Kees Meijs | Nefos 18 Sep '25

18 Sep '25

Hi Stackers, Getting more and more enthusiast about Vector Packet Processor (VPP), I'm curious about real life experience with VPP and L3 routers using Neutron (OVS). Did someone dare to actually do this? 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.

2 2

Putting DB/WAL on SSD on
by William Muriithi 17 Sep '25

17 Sep '25

Hello, We want to use ceph as the openstack storage system and we can afford a purely SSD based storage system. So we are planning to just setup meta data on SSD and leave the data on HDD The documentation around this isn't very clear and wonder if someone can explain a bit Here is what the documentation say:- https://docs.ceph.com/en/reef/start/hardware-recommendations DB/WAL (optional) 1x SSD partion per HDD OSD 4-5x HDD OSDs per DB/WAL SATA SSD <= 10 HDD OSDss per DB/WAL NVMe SSD What does this mean? I am sorry to say, but it look a tad ambiguous to me, but suspect its obvious once one have experience. I have 6 8TB disk per system, and I want to use replication so will end up with 18 OSD I am hoping I don't need 18 SSD as we don't even have enough bays If we can add in 2 800GB SSD per hardware, how do we optimally map those 18 DW/WAL to a total of 6 SSD disks? Regards, William

4 6

[all][elections][tc][ptl][horizon] Combined PTL/TC 2026.1 cycle Election Voting Last Days
by Ian Y. Choi 17 Sep '25

17 Sep '25

We are coming down to the last hours for voting in the TC and Horizon elections. Voting ends Sep 17, 2025 23:45 UTC. Search your Gerrit preferred email address[0] for the messages with subjects like... Poll: OpenStack 2026.1 Cycle Technical Committee Election Poll Poll: OpenStack 2026.1 Cycle - Horizon PTL Election Poll That is your ballot and links you to the voting application. Please vote. If you have voted, please encourage your colleagues to vote. Candidate statements are linked to the names of all confirmed candidates: https://governance.openstack.org/election/ What to do if you don't see the email and have a commit in at least one of the official project teams' deliverable repositories[1]: * check the trash of your gerrit Preferred Email address[0], in case it went into trash or spam * find the ID of at least one commit merged to an official deliverable repo[1] over the current and previous cycles, confirm you are an Open Infrastructure Foundation Individual Member[2], and then email the election officials[3] or get in touch in the #openstack-elections channel on the Freenode IRC network. If we can confirm that you are entitled to vote, we will add you to the voters list and you will be emailed a ballot. Please vote! Thank you, [0] Sign into review.openstack.org and go to Settings > Contact Information. Look at the email listed as your Preferred Email. That is where the ballot has been sent. [1] https://opendev.org/openstack/governance/src/tag/to-be-released/reference/p… [2] https://www.openstack.org/profile/ [3] https://governance.openstack.org/election/#election-officials

1 0

Live-migration never completes memory copy
by Karl Kloppenborg 16 Sep '25

16 Sep '25

Hi Openstack Teams, We’re attempting to live-migrate instances off of a node, we continuously hit a timeout issue where memory copy doesn’t work: 2025-09-12 08:55:20.116 971204 INFO nova.virt.libvirt.driver [None req-250bc815-3323-4619-aef8-a11fdf92b27a 405874cabc5b4bf3912a5f89d54eb0d1 21eb701c2a1f48b38dab8f34c0a20902 - - default default] [instance: 2f496843-a2c4-48d4-bbdc-149a2ea76f1c] Migration running for 274 secs, memory 100% remaining (bytes processed=281505, remaining=8595255296, total=8604033024); disk 100% remaining (bytes processed=0, remaining=0, total=0). 2025-09-12 08:55:58.807 971204 INFO nova.virt.libvirt.driver [None req-250bc815-3323-4619-aef8-a11fdf92b27a 405874cabc5b4bf3912a5f89d54eb0d1 21eb701c2a1f48b38dab8f34c0a20902 - - default default] [instance: 2f496843-a2c4-48d4-bbdc-149a2ea76f1c] Migration running for 312 secs, memory 100% remaining (bytes processed=281505, remaining=8595255296, total=8604033024); disk 100% remaining (bytes processed=0, remaining=0, total=0). 2025-09-12 08:56:02.468 971204 INFO nova.compute.manager [None req-1f91a8d6-1fa7-47b2-8c3f-70925fb7a219 - - - - - -] [instance: 2f496843-a2c4-48d4-bbdc-149a2ea76f1c] During sync_power_state the instance has a pending task (migrating). Skip. 2025-09-12 08:56:37.985 971204 INFO nova.virt.libvirt.driver [None req-250bc815-3323-4619-aef8-a11fdf92b27a 405874cabc5b4bf3912a5f89d54eb0d1 21eb701c2a1f48b38dab8f34c0a20902 - - default default] [instance: 2f496843-a2c4-48d4-bbdc-149a2ea76f1c] Migration running for 352 secs, memory 100% remaining (bytes processed=281505, remaining=8595255296, total=8604033024); disk 100% remaining (bytes processed=0, remaining=0, total=0). 2025-09-12 08:57:17.377 971204 INFO nova.virt.libvirt.driver [None req-250bc815-3323-4619-aef8-a11fdf92b27a 405874cabc5b4bf3912a5f89d54eb0d1 21eb701c2a1f48b38dab8f34c0a20902 - - default default] [instance: 2f496843-a2c4-48d4-bbdc-149a2ea76f1c] Migration running for 391 secs, memory 100% remaining (bytes processed=281505, remaining=8595255296, total=8604033024); disk 100% remaining (bytes processed=0, remaining=0, total=0). 2025-09-12 08:57:56.877 971204 INFO nova.virt.libvirt.driver [None req-250bc815-3323-4619-aef8-a11fdf92b27a 405874cabc5b4bf3912a5f89d54eb0d1 21eb701c2a1f48b38dab8f34c0a20902 - - default default] [instance: 2f496843-a2c4-48d4-bbdc-149a2ea76f1c] Migration running for 431 secs, memory 100% remaining (bytes processed=281505, remaining=8595255296, total=8604033024); disk 100% remaining (bytes processed=0, remaining=0, total=0). Has anyone got insights for this issue? Your help is greatly appreciated. Thanks, Karl. Karl Kloppenborg Chief Technology Officer m: +61 437 239 565 resetdata.com<https://resetdata.com/> [cid:reset_69557fc2-1d63-4932-b5fd-93bd4f39ca7b.png] ResetData supports Mandatory Client Related Financial Disclosures – Scope 3 Emissions Reporting For more information on the phasing of these requirements for business please visit; https://treasury.gov.au/sites/default/files/2024-01/c2024-466491-policy-sta…<https://treasury.gov.au/sites/default/files/2024-01/c2024-466491-policy-sta…> This email transmission is intended only for the addressee / person responsible for delivery of the message to such person and may contain confidential or privileged information. Confidentiality and legal privilege are not waived or lost by reason of mistaken delivery to you, nor may you use, review, disclose, disseminate or copy any information contained in or attached to it. Whilst this email has been checked for viruses, the sender does not warrant that any attachments are free from viruses or other defects. You assume all liability for any loss, damage or other consequences which may arise from opening or using the attachments. If you received this e-mail in error please delete it and any attachments and kindly notify us by immediately sending an email to contact(a)resetdata.com.au<mailto:contact@resetdata.com.au>

4 8

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.2/R-2)
by Goutham Pacha Ravi 16 Sep '25

16 Sep '25

Hello Stackers, We're two weeks away from the date of the coordinated 2025.2 "Flamingo" release [1]. At this time, nearly all deliverables that follow the "cycle-with-rc" release model [2] have shipped their first release candidate. Over the next couple of weeks, OpenStack project teams will be expected to test, find and resolve any release blockers in these deliverables. The ongoing elections to fill four seats on the OpenStack Technical Committee and to elect a PTL for the OpenStack Dashboard ("Horizon") project team will conclude at 23:45 UTC on September 17, 2025 [3]. If you haven't already voted, please do so. There were no new governance proposals that were merged in the past week. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee was held on September 9, 2025 [4]. We discussed project teams that had no PTL candidates in the ongoing renewal exercise: Vitrage, OpenStack Charms, Venus, and Monasca. You are all aware that we began the retirement process for the Monasca team [5] and are actively considering a maintainer request. We expect to make a decision past the 2025.2 "Flamingo" coordinated release. We have had a call for help [6][7][8] advertisement for the other projects and will discuss alternatives if those go unanswered. The TC discussed efforts to increase voter turnout for OpenStack elections by encouraging people to opt in to CIVS emails. A related topic was the reduced electorate, which was suspected to be due to OpenInfra Foundation (OIF) membership renewal requirements. The committee agreed to follow up on this after the elections conclude. We discussed default MySQL/MariaDB charset/collation changes that affect most OpenStack service projects. A few key points were discussed, including the need for a potential community goal to migrate from utf8 (which aliases to utf8mb3) to utf8mb4 due to MariaDB's plan to remove the utf8 alias. The meeting also addressed a known issue with Ironic, which has conflicts with the larger utf8mb4 type due to index size limitations. We decided to gather more data on what each project is currently using to better understand the scope of the problem. Dmitriy Robotyogev (noonedeadpunk) and Seunghun Lee (seunghunlee) volunteered to collect this information and add it to a new Etherpad [9] that will inform next steps. After the meeting, Jonathan Wright (JonathanWright[m]) from AlmaLinux joined us to discuss the potential for adding AlmaLinux to OpenStack's supported runtimes, noting its benefits like support for older CPUs (AlmaLinux 10 continues to support older CPUs like x86-64-v2) and more stable CI mirrors compared to CentOS Stream. This could be a significant benefit for OpenStack's CI (Continuous Integration) providers, as it would allow them to utilize their existing, aging hardware more effectively for testing. Community contributors from AlmaLinux want to improve its integration with OpenStack, including creating tailored cloud images for CI and contributing infrastructure resources. We agreed that a clear goal is to establish a working relationship with AlmaLinux volunteers to create and maintain CI images. This effort would likely involve a "pop-up team" to handle the initial implementation, with a long-term plan for AlmaLinux contributors to take ownership of the testing infrastructure. The primary objective is ensuring OpenStack services and deployments can be reliably tested and deployed on AlmaLinux, thereby expanding the project's supported user base. If you're interested to be a part of this effort, please chime in on the #openstack-tc channel on OFTC. The next meeting of the OpenStack Technical Committee is on Tuesday, September 16, 2025, at 1700 UTC. It will be hosted on the #openstack-tc IRC channel on OFTC. Please find the meeting's agenda on the OpenStack wiki [10]. I hope you'll be able to join us there. === Governance Proposals === ==== Open For Review ==== - Retire metalsmith project from bare metal program | https://review.opendev.org/c/openstack/governance/+/958297 - Retire Monasca project | https://review.opendev.org/c/openstack/governance/+/953671 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - Extend Monasca's inactive state | https://review.opendev.org/c/openstack/governance/+/959392 === Upcoming Events === - 2025-09-17: OpenStack TC and Horizon project elections conclude: https://governance.openstack.org/election/ - 2025-10-01: OpenStack 2026.1 "Flamingo" release day - 2025-10-03: OpenStack's Birthday Meetup, Austin: https://www.meetup.com/openinfra-austin/events/310508680 - 2025-10-17: OpenInfra Summit, Paris-Saclay: https://summit2025.openinfra.org/ - 2025-10-27: OpenInfra PTG: https://openinfra.org/ptg/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.2 "Flamingo" Release Schedule: https://releases.openstack.org/flamingo/schedule.html [2] "cycle-with-rc" release model: https://releases.openstack.org/reference/release_models.html#cycle-with-rc [3] OpenStack Elections: https://governance.openstack.org/election/ [4] TC Meeting IRC Log, Sep 9, 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-09-09-17.00.html [5] Retire Monasca project: https://review.opendev.org/c/openstack/governance/+/953671 [6] PTL needed for OpenStack Vitrage: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [7] PTL needed for OpenStack Charms: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [8] PTL needed for OpenStack Venus: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [9] Dealing with Mariadb/Mysql changes: https://etherpad.opendev.org/p/gazpacho-collations-charsets [10] TC Meeting Agenda, Sep 16, 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[neutron] Bug deputy report for week of September 8th
by Brian Haley 16 Sep '25

16 Sep '25

Hi, I was the Neutron bug deputy last week. Below is a short summary about the reported bugs. -Brian Critical bugs ------------- * None High bugs --------- * https://bugs.launchpad.net/neutron/+bug/2122483 - [FT][OVN] ``TestOvn*Sync*`` test failing due to missing IDL lock - https://review.opendev.org/c/openstack/neutron/+/960384 * https://bugs.launchpad.net/neutron/+bug/2122429 - [logapi] ``_check_port_bound_sg`` called outside a READER context - https://review.opendev.org/c/openstack/neutron/+/960271 * https://bugs.launchpad.net/neutron/+bug/2122505 - [OVN][FT] The "Chassis_Private" register contains not expected values in the metadata tests - https://review.opendev.org/c/openstack/neutron/+/960369 * https://bugs.launchpad.net/neutron/+bug/2122524 - [FT] Random fails with ``test_ovs_bridge_name_not_set_if_integration_bridge_not_set`` - Needs owner * https://bugs.launchpad.net/neutron/+bug/2122525 - [FT] Test ``test_create_floatingip_port_forwarding_and_remove_subnets`` randomly failing - Needs owner * https://bugs.launchpad.net/neutron/+bug/2122651 - [FT] ``DBConnectionError`` exception during the ``OpportunisticSqlFixture`` cleanup process - https://review.opendev.org/c/openstack/neutron/+/960727 Medium ------ * https://bugs.launchpad.net/neutron/+bug/2122495 - [OVS Firewall] some flows, IPs from allowed_address_pairs, are dropped after neutron-openvswitch-agent service restart due to CT_MARK=0x1 - https://review.opendev.org/c/openstack/neutron/+/960602 * https://bugs.launchpad.net/neutron/+bug/2122606 - neutron-tempest-plugin-designate-scenario job fails to run due to over-restricted irrelevant files - https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/960659 * https://bugs.launchpad.net/neutron/+bug/2122706 - TestOVNNeutronAgentBase functional tests use system ovsdb - https://review.opendev.org/c/openstack/neutron/+/960892 Low --- * None Wishlist -------- * None

1 0

[neutron][taas][taap-as-a-service] moving client to seperate package
by Mohammed Naser 15 Sep '25

15 Sep '25

Hi there, It seems that at the moment, tap-as-a-service package contains both the server and the client components, which means that if you are trying to pull in the CLI components, you end up with Neutron as well, which is quite heavy. Is there a reason behind it that decision or is this something that someone needs to get around doing but no one has? Thanks, Mohammed

2 4

[all] No documentation for the API wsgi entry point of project APIs
by Thomas Goirand 13 Sep '25

13 Sep '25

Hi, As we're supposed to move away from uwsgi's config: wsgi-script=/usr/bin/<something> I'm switching all (-most every) Debian package to: module=<something-else> in the shipped <project>-api-uwsgi.ini file. In some case, that's fine, the release note tells where to find it. However, in a general way, it's documented nowhere but in the release note. In some cases, like for Magnum, the release note only tells that the wsgi-script is deprecated, without even telling to what I should switch. I've double-guessed that it should be: magnum.wsgi.api:application as this is what devstack/lib/magnum is doing. But I'm not sure, and I'll have to check for that fact after my package is built. Someone told me on IRC that I was right, and that this path is probably the "standard" for all projects. One shouldn't have to hunt for this kind of information. Could we agree on a *STANDARD* way to document this in every project? Or at least document somewhere OpenStack wide, that the standard path *must* be: magnum.wsgi.api:application and that distros and operators should expect it? Or is it that I missed the information and that's already documented? If that's the case, where is it? Cheers, Thomas Goirand (zigo)

4 4

[masakari]HACluster Containers Failing
by Thamanna Farhath 13 Sep '25

13 Sep '25

Hi OpenStack Community, I have installed *Masakari* using Kolla-Ansible, and after that I also installed *HACluster*. However, the HACluster containers are failing and keep exiting. Setup: - 3 controller nodes - Multiple compute nodes - Deployment: Kolla-Ansible My questions are: 1. Do I really need Masakari together with HACluster for instance HA? 2. Is there an alternative or recommended way to deploy HACluster with Kolla-Ansible? 3. Has anyone faced the issue where HACluster containers keep exiting after deployment? Any guidance, troubleshooting tips, or experiences would be very helpful Thanks, Thamanna Farhath N Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

2 1

[release] Release countdown for week R-2
by Thierry Carrez 12 Sep '25

12 Sep '25

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for (almost) all the 2025.2 "Flamingo" deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- Early in the week, the release team will be proposing stable/2025.2 branch creation for all deliverables that have not branched yet, using the latest available 2025.2 "Flamingo" release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/2025.2 branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/2025.2 branch before releasing out of the stable/2025.2 branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for 2026.1 "Gazpacho" development, though the focus should still be on finishing up 2025.2 "Flamingo" until the final release. Opening up the new development cycle is also a good opportunity to teams to revise their zuul jobs and used nodesets and clean up all unnecessary ones. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final 2025.2 "Flamingo" release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targeted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the 2025.2 "Flamingo" version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: September 26th, 2025 (R-1 week) Final 2025.2 "Flamingo" release: October 1st, 2025 OpenInfra Summit Europe: October 17th-19th, 2025 -- Thierry Carrez (ttx)

1 0

[nova] CPU extra flag invalid
by Kees Meijs | Nefos 12 Sep '25

12 Sep '25

Hi list, On a Compute Node we're seeing the following: > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service Traceback > (most recent call last): > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service File > "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line > 788, in _check_cpu_compatibility > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service > self._compare_cpu(cpu, self._get_cpu_info(), None) > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service File > "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line > 9029, in _compare_cpu > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service raise > exception.InvalidCPUInfo(reason=m % {'ret': ret, 'u': u}) > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service > nova.exception.InvalidCPUInfo: Unacceptable CPU info: CPU doesn't have > compatibility. > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service 0 > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service Refer to > http://libvirt.org/html/libvirt-libvirt-host.html#virCPUCompareResult > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service During > handling of the above exception, another exception occurred: > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service Traceback > (most recent call last): > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service File > "/usr/lib/python3/dist-packages/oslo_service/service.py", line 807, in > run_service > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service service.start() > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service File > "/usr/lib/python3/dist-packages/nova/service.py", line 159, in start > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service > self.manager.init_host() > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service File > "/usr/lib/python3/dist-packages/nova/compute/manager.py", line 1421, > in init_host > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service > self.driver.init_host(host=self.host) > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service File > "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line > 723, in init_host > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service > self._check_cpu_compatibility() > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service File > "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line > 794, in _check_cpu_compatibility > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service raise > exception.InvalidCPUInfo(msg) > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service > nova.exception.InvalidCPUInfo: Configured extra flag: ibpb it not > correct, or the host CPU does not support this flag. Please correct > the config and try again. Unacceptable CPU info: CPU doesn't have > compatibility. > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service 0 > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service Refer to > http://libvirt.org/html/libvirt-libvirt-host.html#virCPUCompareResult > 2025-09-12 15:10:37.052 735327 ERROR oslo_service.service This is very interesting, since the CPU supports the ibpb flag for sure (i.e. /proc/cpuinfo cleary lists the feature). Manually adding: > <feature policy="require" name="ibpb"/> to the XML definition works and libvirt is happy. Is there some other name or alias for ibpb we should use? 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

[requirements]Flamingo pyroute2 regression
by Balazs Gibizer 12 Sep '25

12 Sep '25

Hi requirements folks, We identified a bug[1] in pyroute2 0.9.1 that causes intermittent failures during interface attach / detach operations. Originally we got the indication that the pyroute2 0.9.4 fixed the issue and our tests showed green results so we bumped to that version. But since then we observed that the problem still happens in 0.9.4 as well. Can we roll back our pyroute2 dependency to < 0.9 in Flamingo so close to the release? If not, can we later roll back the requirement on stable/2025.2? Or the only way is to roll forward on stable/2025.2 (and on master) when the fix appears in pyroute2? Thanks, gibi [1]https://bugs.launchpad.net/os-vif/+bug/2109396

6 10

[nova]Guidance on Instance Migration Issues in Production
by Thamanna Farhath 12 Sep '25

12 Sep '25

Hi All, I’m facing some issues with instance migration in production and need advice: Migrations are taking longer than expected—any tips to handle delays? When the host is fully utilized or overcommit ratio is high, migration sometimes fails with "valid host not found". Are there other common causes? Can we use a separate network interface for migration in OpenStack, and is it recommended? Any guidance or references would be appreciated. Thanks, Thamanna Farhath N https://www.facebook.com/Zybisys/ Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

2 1

[nova]Hypervisor Data and Overcommit Ratio via API
by Thamanna Farhath 12 Sep '25

12 Sep '25

Hi All, I noticed a mismatch between hypervisor data shown in Horizon and via the OpenStack API. The API returns original values without calculating the overcommit ratio. Could you advise how to retrieve the effective resources including overcommit ratio via the API? Thanks, Thamanna Farhath N Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

2 1

[cinder]Issue Deleting Volume Snapshots in OpenStack
by Thamanna Farhath 11 Sep '25

11 Sep '25

Hi All, I’m facing an issue when deleting volume snapshots in our OpenStack environment (Kolla-Ansible + Ceph). The snapshots get stuck in error deleting status. Logs show: rbd.PermissionError: [errno 1] RBD permission error (error unprotecting snapshot b'volume-<id>'@b'snapshot-<id>') Could you suggest ways to resolve this or reduce such permission errors during snapshot deletion? Thanks Thamanna Farhath N https://www.facebook.com/Zybisys/ Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender. E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

1 0

[publiccloud-sig] Public Cloud SIG meeting d.d. 10 September
by Kees Meijs | Nefos 11 Sep '25

11 Sep '25

Hello Stackers, Tomorrow (that's 10 September) the bi-weekly Public Cloud SIG meeting will be held again. The publicly available video meeting will be conducted from 07:00 hrs UTC (09:00 hrs CEST) and on 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.

2 2

[sdk][requirements] RFE requested for openstacksdk
by Stephen Finucane 11 Sep '25

11 Sep '25

o/ Per request from elodilles, I'd like to request a Requirements Freeze Exception (RFE) for openstacksdk in order to release [1]. That resolves a minor bug that is currently preventing us bumping the minimum version of openstacksdk before we release Flamingo [2]. fwiw, 4.7.0 itself consists mainly of wholly new features, bug fixes, and test cleanup. I've includes the git log below Cheers, Stephen [1] https://review.opendev.org/c/openstack/releases/+/960355 [2] https://review.opendev.org/c/openstack/requirements/+/960027 --- ❯ git log --oneline --no-merges 4.6.0..4.7.0 -- . ':!openstack/tests' ':!doc' 53e19fe0a Add id to query_mapping for Networking 2d8ff6603 Add SDK support for ``glance image-tasks`` 61323654e tests: Use binary mode to open files 1649ed0cd Replace CLA with DCO b14c73d35 Remove commented out sections b2ada579c create_image: support other import methods d649aada8 resource: add max_items parameter to resource cb04f4a70 Fix hostname attribute withing request body c2465fee2 Increase swap allocation for devstack-networking 4b0b78e19 Allow filtering of volumes by properties 3a774c1c5 Fix Volume.set_image_metadata 82bc00507 Remove loop variable 65a97e1a7 Fix create_volume_snapshot() description. 83fc95d25 Remove duplicate Python version declarations 2eb367c6e Migrate setup configuration to pyproject.toml da4961cab zuul: Make openstacksdk-functional-devstack-masakari voting 198cb9e02 zuul: Make openstacksdk-functional-devstack-ironic voting 07f52229b Clean small nit comment ad9896c12 Add support for inspection rules 4b74d73ae Add backup export command 5a909ee17 typing: Annotate openstack.config.openstackcloud 7c1e42b41 config: Handle interface list in CloudRegion.get_all_version_data 36a7ccb6f typing: Annotate openstack.config.cloud_config 550c15c83 typing: Annotate openstack.config.loader 5a2b3bd81 typing: Annotate openstack.config.vendors 9afc09407 typing: Annotate openstack.config.cloud_region de9129e76 Update .git-blame-ignore-revs b82a434d3 Follow-up: Add support for runbooks

2 1

[cinder] IBM SVf driver callhome
by Vivek Pandey 10 Sep '25

10 Sep '25

Hi Joe/ Brian, Since we didn’t get a chance to discuss the patch [IBM SVf driver] Adding support for callhome plugin, we can continue the conversation here. Patch : https://review.opendev.org/c/openstack/cinder/+/951829. We need callhome enabled as default for which we have introduced a parameter “callhome” in cinder.conf. This feature is to fecth the os_version, cinder-manage version and ispbhaenabled. Note: We are not fetching any customer’s sensitive data. Please let me know if you’ve had a chance to review NetApp’s ActiveIQ implementation. Netapp’s ActiveIQ code ref : https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/netap… As we have discussed during the 9th July cinder call, Anoop from NetApp confirmed that they are enabling it by default and EMS details are being captured from the logs. Based on that, do you think we can align or extend our current IBM callhome implementation (from the patch above) to follow a similar approach? Thanks, Vivek

5 9

OpenStack wide MariaDB 11.8 problem
by Seunghun Lee 10 Sep '25

10 Sep '25

Dear OpenStack developers I'm a Kolla contributor and was trying to bump MariaDB from 10.11 to 11.8 for Kolla and Kolla-Ansible projects. During this, I found problems that can happen across the whole OpenStack services with MariaDB's default charset and collation set changes. Here's the note I made for each problem I found. Problems with default collation set change - MariaDB changed default collation set of charset utf8mb3 from utf8mb3_general_ci to utf8mb3_uca1400_ai_ci from 11.5 https://jira.mariadb.org/browse/MDEV-25829 - K-A currently sets database level charset to utf8 (Which is aliased to utf8mb3) and collation set to utf8_general_ci (aliased to utf8mb3_general_ci) - Problem detected when deploying fresh magnum on MariaDB 11.8: https://bugs.launchpad.net/magnum/+bug/2121797 - This is because how MariaDB works. If charset is not specified when creating a table, MariaDB uses database level charset and collation set (if set) or server level charset and collation set - If only charset is specified when creating a table, MariaDB uses MariaDB default (defined as a list of mapping in variable ``collation_connection``) - Magnum specified charset when creating *some* of tables not all -> Collation set inconsistency in magnum database. - Server-wide collation set inconsistency (when DB and services are freshly deployed) - Some services such as Nova, Keystone, Cinder, designate provides charset when creating tables (Also alters database level charset to utf8 in first alembic op) Let's call them group A - Some services such as Glance, Neutron, Octavia, Placement don't. Let's call them group B - Then we have Magnum which mixed up. Let's call it... Magnum - These differences cause database level collation set inconsistency between group A and group B services because of MariaDB's behaviour on creating a table and database - Potential problem for MariaDB 10.11 to 11.8 upgrade - Existing databases in MariaDB server have collation set of utf8mb3_general_ci - Because of MariaDB's new default collation set for utf8mb3 and how the table creation works, if any services decide to create a new table, they can be created with utf8mb3_uca1400_ai_ci and causes collation set inconsistency - This issue can be invisible at first but if any project decides to create new tables then do string comparison between the old tables and new tables, it will be visible - Potential solution A: Override MariaDB default for utf8mb3 to utf8mb3_general_ci for each service clients https://mariadb.com/docs/server/reference/data-types/string-data-types/char… - Pros: Easy - Cons: - In fact, it doesn't work. Because there are slight differences on how each projects create tables, only some of them (Keystone, designate) are affected - Even if it worked, It's just delaying the problem. Looks like community pushed forward in the past: https://review.opendev.org/c/openstack/kolla-ansible/+/455154 - Potential solution B: Change K-A's server level collation set config to utf8mb3_uca1400_ai_ci then migrate (ALTER TABLE) all tables to use new collation on upgrade - Pros: We'll probably don't need to worry about this matter for a long time - Cons: - Service disruption, inter-table relationships such as foreign keys make altering table hard. - Percona-toolkit claims it can be done with near-zero downtime with FK handling strategies. Can be useful. https://docs.percona.com/percona-toolkit/pt-online-schema-change.html (GPLv2 license) - Potential solution C: Use MariaDB 11.4 instead - Pros: 11.4 is also an LTS but without this drama - Cons: Not the latest LTS Problems with default character set change - MariaDB's new default charset utf8mb4 https://jira.mariadb.org/browse/MDEV-19123 - This is not urgent but MariaDB is planning to remove alias between utf8 and utf8mb3 https://jira.mariadb.org/browse/MDEV-30041 - Currently most of openstack projects use 'utf8' when specifying a character set not 'utf8mb3'. This will all need to be updated to 'utf8mb3'. - Or we can try moving on to utf8mb4 but ironic need to use utf8mb3 due to its internal design https://docs.openstack.org/ironic/latest/install/install.html#set-up-the-da… - Transition to utf8mb4 would also need a migration plan - Using MariaDB 11.4 also helps here because this change is from 11.6 I suggest to raise this topic on next OpenStack TC meeting. I think it's worth having a inter-project conversation as these will affect any projects that uses DB. What do people think about this? Any inputs are appreciated. Kind regards, Seunghun Lee Cloud Engineer, StackHPC

4 4

[freezer] Activity on this project?
by Jimmy McArthur 09 Sep '25

09 Sep '25

Are there orgs or individuals that are working on Freezer and/or have interest in working on Freezer? Cheers, Jimmy

4 3

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.2/R-3)
by Goutham Pacha Ravi 09 Sep '25

09 Sep '25

Hello Stackers, We're three weeks away from the coordinated 2025.2 "Flamingo" release [1]. This week, project teams are testing code changes and merging bug fixes to deliver release candidates for deliverables that follow a "cycle-with-rc" release model [2]. Polls for electing a PTL for the OpenStack Dashboard ("Horizon") project team, as well as for four members to the OpenStack Technical Committee, are still open. They will close on September 17th, 2025, at 23:45 UTC [3]. In the past week, election officials reached out to a section of the electorate that hadn't opted in to emails on the election system: CIVS. Please do contact the election officials [3] if you are having trouble finding your ballot. Besides this, governance updates included marking the conclusion of the goal to migrate WSGI scripts across all OpenStack services [4] and adding new metadata to project tracking to highlight inactive OpenStack projects. This will help us make release and documentation updates to clearly flag deliverables that need help from new (or existing) contributors, as well as serve as a health indicator to operators and users. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee occurred on September 2nd, 2025, simultaneously over Meetpad [5] and IRC [6]. The "Migrate from WSGI scripts to module paths" goal was completed [4]. A significant portion of the meeting was spent discussing the proposed retirement of the Monasca project team. The TC considered whether to recommend forking the project into a new namespace on opendev.org under the aegis of the volunteer who wants to maintain it. We also discussed the need to update documentation and README files to reflect the project's maintenance status and to implement automated updates for this process. We discussed the ongoing elections, where an early retrospective item was to urge existing members to renew their OpenInfra Foundation memberships and to opt in to CIVS emails. The team reviewed "leaderless teams" and the status of projects like Vitrage, Venus and OpenStack Charms, noting that a PTL candidate is still needed. We took an action item to tag retired packages on PyPi as part of the repository retirement process. Finally, the group briefly touched on gate health issues related to Debian Trixie nodes and a new discussion point about default MySQL/MariaDB charset/collations that will be addressed in the next meeting. The next meeting of the OpenStack TC is on September 9th, 2025, at 1700 UTC. This meeting will be hosted in the #openstack-tc channel on OFTC. Please find the meeting's agenda on its wiki page [7]. I hope you'll be able to join us there. === Governance Proposals === ==== Merged ==== - Show inactive project status in project.yaml | https://review.opendev.org/c/openstack/governance/+/958229 - Mark "Migrate from WSGI scripts" goal as completed | https://review.opendev.org/c/openstack/governance/+/958817 ==== Open For Review ==== - Retire metalsmith project from bare metal program | https://review.opendev.org/c/openstack/governance/+/958297 - Retire Monasca project | https://review.opendev.org/c/openstack/governance/+/953671 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - Extend Monasca's inactive state | https://review.opendev.org/c/openstack/governance/+/959392 === Upcoming Events === - 2025-09-09: OIF Board Monthly meeting: https://board.openinfra.org/ - 2025-09-17: OpenStack TC and Horizon project elections conclude: https://governance.openstack.org/election/ - 2025-10-01: OpenStack 2026.1 "Flamingo" release day - 2025-10-03: OpenStack's Birthday Meetup, Austin: https://www.meetup.com/openinfra-austin/events/310508680 - 2025-10-17: OpenInfra Summit, Paris-Saclay: https://summit2025.openinfra.org/ - 2025-10-27: OpenInfra PTG: https://openinfra.org/ptg/ === How to Contact the TC === You can reach the TC in several ways: - Email: send an email with the tag [tc] on this mailing list. - Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC. - Join us at our weekly meeting: The Technical Committee meets every week on Tuesdays at 1700 UTC [7]. Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.2 "Flamingo" Release Schedule: https://releases.openstack.org/flamingo/schedule.html [2] "cycle-with-rc" release model: https://releases.openstack.org/reference/release_models.html#cycle-with-rc [3] OpenStack Elections: https://governance.openstack.org/election/ [4] Community Goal to update WSGI configuration: https://governance.openstack.org/tc/goals/proposed/migrate-from-wsgi-script… [5] TC Meeting Video Recording, Sep 2nd, 2025: https://youtu.be/K_tdk4mkxT0 [6] TC Meeting IRC Log, Sep 2nd, 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-09-02-17.01.html [7] TC Meeting Agenda, Sep 9th, 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[watcher] Core team updates - removals, reminders, and new addition
by Sean Mooney 09 Sep '25

09 Sep '25

Hi everyone, I'm writing to propose some updates to the Watcher core team membership to ensure we maintain an active and engaged core review team. ## Proposed Removals (Immediate) The following core reviewers have been inactive for an extended period and I propose to remove them from all Watcher core groups: * Alexander Chadin (joker946(a)gmail.com) - last contribution: 26 Feb 2019 https://www.stackalytics.io/?module=watcher-group&release=all&user_id=joker… <https://www.stackalytics.io/?module=watcher-group&release=all&user_id=joker…> * Vincent Françoise (Vincent.FRANCOISE(a)b-com.com) - last contribution: 15 Mar 2019 https://www.stackalytics.io/?module=watcher-group&release=all&user_id=vince… <https://www.stackalytics.io/?module=watcher-group&release=all&user_id=vince…> * YumengBao (yumeng_bao(a)yahoo.com) - last contribution: 09 Apr 2020 https://www.stackalytics.io/?module=watcher-group&release=all&user_id=yumen… <https://www.stackalytics.io/?module=watcher-group&release=all&user_id=yumen…> * aditi sharma (adi.sky17(a)gmail.com) - last contribution: 22 Nov 2018 https://www.stackalytics.io/?module=watcher-group&release=all&user_id=adi-s… <https://www.stackalytics.io/?module=watcher-group&release=all&user_id=adi-s…> * licanwei (li.canwei2(a)zte.com.cn) - last contribution: 21 Jan 2021 https://www.stackalytics.io/?release=all&user_id=li-canwei2&module=watcher-… <https://www.stackalytics.io/?release=all&user_id=li-canwei2&module=watcher-…> * suzhengwei (sugar-2008(a)163.com) - last contribution: 13 Sep 2022 https://www.stackalytics.io/?module=watcher-group&release=all&user_id=sue.s… <https://www.stackalytics.io/?module=watcher-group&release=all&user_id=sue.s…> We want to thank all these contributors for their valuable work and contributions to the Watcher project over the years for there time and effort. ## Core Activity Notice (Removal planned for 2026.2) The following core reviewers are currently showing low activity levels. We're providing advance notice that they will be removed from the core group at the start of the 2026.2 cycle unless they become active again during the 2026.1 cycle: * chenker (chen.ke14(a)zte.com.cn) * Dan Smith (dms(a)danplanet.com) * Marios Andreou (marios.andreou(a)gmail.com) * Slawek Kaplonski (skaplons(a)redhat.com) We recognize that over time priorities change, if you wish to maintain their core status and can re-engage or wish to be be removed before we review the core composition again at the start of 2026.2 just let us know. ## New Core Proposal I would also like to propose adding jgilaber (jgilaber(a)redhat.com) as a new member of the watcher-core group, based on their recent contributions and engagement with the project. ## Timeline These changes will take effect if there are no objections by our next Watcher IRC meeting on Thursday, September 11th, 2025. Please share any feedback or concerns about these proposed changes. Regards sean

4 3

October 2025 PTG Team Signup Final Call
by Kendall Nelson 09 Sep '25

09 Sep '25

Hello Everyone, Make sure to sign your team up for the next virtual Project Teams Gathering (PTG), which will be held from Monday, October 27th to Friday, October 31st 2025! If you haven't already done so and your team is interested in participating, you need to complete the survey[1] by September 14th, 2025 at 7:00 UTC. Please also make sure to register[2] for the event - it’s free :) Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2025_ptg_survey [2] PTG Registration: http://ptg.openinfra.dev/

1 0

[neutron] Bug deputy - week of September 1st
by Sławek Kapłoński 08 Sep '25

08 Sep '25

Hi, It was pretty quiet week. Here are details about what happened: ### High - https://bugs.launchpad.net/neutron/+bug/2122065 - ovs agent missing openflow rules due to python error - assigned to Brian, fix proposed https://bugs.launchpad.net/neutron/+bug/2122065 ### Medium - https://bugs.launchpad.net/neutron/+bug/2122110 - [FT] Random errors in OVN ``TestMetadataAgent`` tests - assigned to Rodolfo, fix already proposed, - https://bugs.launchpad.net/neutron/+bug/2122079 - DHCP agent incorrectly releasing leases due to missing client_id - unassigned, Brian already commented there but solution for this may not be that easy to figure out according to the bug report and Brian's comment, ### Low - https://bugs.launchpad.net/neutron/+bug/2121935 - [FT] Random ``DBReferenceError`` errors in the functional tests Edit - assigned to Rodolfo, fix already proposed - https://bugs.launchpad.net/neutron/+bug/2122107 - [FT] Test ``test_initialize_network_segment_range_support_parallel_execution`` failing in the eventlet-removal patch - assigned to Rodolfo, ### To triage - https://bugs.launchpad.net/neutron/+bug/2121961 - Duplicate packet logs with openvswitch driver Edit - I asked Elvira to take a look at it. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Making WIP patch Active (without owner)
by Nimesh Desai 08 Sep '25

08 Sep '25

After the resolving the merge conflict, the following IBM Cinder driver patch is now in ‘Work in Progress’ state. We want to now make it Active, but the owner of the patch is no longer working with the organisation. Thus, the Gerrit UI is not showing option to publish. How to make this patch Active again? The patch was reviewed and had multiple +1 votes earlier. Patch: https://review.opendev.org/c/openstack/cinder/+/879839

6 8

[qa] PTL/Tempest core on PTO
by Ghanshyam Maan 06 Sep '25

06 Sep '25

Hi All, I would like to let you know that I will be on PTO and will return after the 2025.2 release. I will try to check IRC occasionally for any urgent changes that require merging, particularly in Tempest (as there is no other active core). -gmaan

1 0

[release] Release countdown for week R-3
by Thierry Carrez 05 Sep '25

05 Sep '25

Development Focus ----------------- The Release Candidate (RC) deadline is next Friday, September 12th, 2025. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/2025.2 branch will be cut. This branch will track the 2025.2 "Flamingo" release. Once stable/2025.2 has been created, the master branch will be ready to switch to 2026.1 "Gazpacho" development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing 2025.2 "Flamingo" plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/2025.2 branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from the master branch. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/2025.2 branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from the master branch (which will technically then be 2026.1 "Gazpacho") to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any 2025.2 "Flamingo" release so far. Finally, now is a good time to finalize release highlights. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: September 12th, 2025 (R-3 week) Final RC deadline: September 26th, 2025 (R-1 week) Final 2025.2 "Flamingo" release: October 1st, 2025 OpenInfra Summit Europe: October 17th-19th, 2025 -- Thierry Carrez (ttx)

1 0

[qa][ptg] Call for 2026.1 vPTG QA topic
by Ghanshyam Maan 05 Sep '25

05 Sep '25

Hi All, I have created the etherpad to collect the QA topics for the coming vPTG (2026.1 cycle). Based on the topics, we will decide if we need any slot in PTG. Feel free to add your topics before Sept 12th. - https://etherpad.opendev.org/p/qa-2026.1-ptg -gmann

1 0

[oslo] status of eventlet removal for oslo.service?
by Chris Friesen 05 Sep '25

05 Sep '25

Hi everyone, Looking at the "epoxy" spec for removing Eventlet from oslo.service (https://specs.openstack.org/openstack/oslo-specs/specs/epoxy/remove-eventle…) the very top line is a link to search blueprints.launchpad.net. Following that link it seems like there is no blueprint for removing eventlet from oslo.service, so does the spec itself (with the proposed milestones) represent the current plan? Separately, is there somewhere that shows the progress on the threading backend for oslo.service? I see it exists, are there any limitations on the current implementation? Thanks, Chris

2 1

[ops][nova][neutron] Routed provider networking and physnet port scheduling
by Nathan Harper 04 Sep '25

04 Sep '25

Hi all, We have been looking at building some routed provider networks, following this documentation: https://docs.openstack.org/neutron/latest/admin/config-routed-networks.html In this scenario we have 4 racks, and have defined physnets for each rack and assigned SRIOV interfaces for each. We then have created a multisegment network, with a segment associated with each physnet. We get the expected resource provider in placement containing only these hypervisors. When scheduling instances onto this network, the allocation candidates are any hypervisors in racks 1-4 (openstack filters the hypervisors using the aggregates for each segment that neutron creates). However, during instance build the pci device request sent to nova-compute always contains the physnet of the same segment. Debugging the builds, we ended up here: https://opendev.org/openstack/nova/src/branch/master/nova/network/neutron.p…, with: # TODO(vladikr): Additional work will be required to handle the # case of multiple vlan segments associated with different # physical networks. Which originates from this commit: https://opendev.org/openstack/nova/commit/b9d9d96a407db5a2adde3aed81e61cc95… This suggests that despite the documentation describing using multiple VLAN backed segments in this fashion, this has never worked? Or are we missing something? Has anyone successfully used routed provider networks? -- Regards, Nathan Harper Principal Engineer – Cloud Development Platform Engineering nathanh(a)graphcore.ai<mailto:nathanh@graphcore.ai> www.graphcore.ai →<http://www.graphcore.ai/> ** We have updated our privacy policy, which contains important information about how we collect and process your personal data. To read the policy, please click here<http://www.graphcore.ai/privacy> ** This email and its attachments are intended solely for the addressed recipients and may contain confidential or legally privileged information. If you are not the intended recipient you must not copy, distribute or disseminate this email in any way; to do so may be unlawful. Any personal data/special category personal data herein are processed in accordance with UK data protection legislation. All associated feasible security measures are in place. Further details are available from the Privacy Notice on the website and/or from the Company. Graphcore Limited (registered in England and Wales with registration number 10185006) is registered at, 1 Maple Road, Bramhall, Stockport, Cheshire, UK, SK7 2DH. This message was scanned for viruses upon transmission. However Graphcore accepts no liability for any such transmission.

3 7

[release][horizon][ironic] Deliverables potentially needing a refresh before final Flamingo release
by Thierry Carrez 04 Sep '25

04 Sep '25

Quick reminder that for deliverables following the cycle-with-intermediary model, the release team will use the latest Flamingo release available on release week. The following deliverables have done a Flamingo release, but it was not refreshed in the last two months: - horizon (25.4.0 was released 2025-05-27) - ironic-python-agent-builder (6.1.0 was released 2025-06-10) - networking-baremetal (6.6.0 was released 2025-06-10) You should consider making a new one very soon, so that we don't use an outdated version for the final release. -- Thierry Carrez (ttx)

1 0

#eventlet-removal - Progress & Updates - Flamingo Past Milestone 3
by Herve Beraud 03 Sep '25

03 Sep '25

TL;DR: We just recently passed Flamingo's milestone 3 and since the last ML update we observed tremendous progress. Ironic, Barbican, Heat completed their migration. Futurist has been improved with new useful features for threading mode. The migration timeline has been adjusted to match Nova's dual mode support. PTG is under preparation. Statistics show good progress. Eventlet now supports Python 3.14. ## OpenStack Updates From a statistical perspective: - almost 17% of the occurences of the runtime code initially impacted by Eventlet have been tackled — outside of code dedicated to test, doc, releasenotes, etc; - if we include all the spectrum of occurrences to migrate — code, tests, doc, examples — it represent ~14% of the entire code base already migrated; - more than 40% of all impacted repositories have made some progress in link with the migration; - 13 projects have been fully migrated since the beginning; - more than 332 patches related to the eventlet migration have been submitted to gerrit. From the teams perspective, we can highlight Ironic completed its migration, for the occasion wrote an excellent write-up [1] — thanks Julia — I strongly encourage you to read it. Barbican [2] and heat [3] successfully completed their migrations too. They are now fully threading based. Dmitry in collaboration with the Ironic team implemented a DynamicPoolExecutor in Futurist [4]. It helps replace dynamic GreenPool. Oslo.service's backend system is now documented [5]. There is still ongoing work on several OpenStack deliverables: Neutron, Nova, Manila, Magnum, Mistral, Watcher, Designate, Trove, etc. All these teams demonstrated awesome progress. The migration timeline has been adjusted at the governance level to match Nova's dual mode support [6]. There is ongoing preparation of the PTG sessions. I think there will be a short slot during one of the TC sessions, and surely a fully dedicated one hour slot to host cross team open discussions. ## Eventlet Updates The support of Python 3.14 has been introduced within Eventlet 0.40.2. A vulnerability (CVE-2025-58068, CVSS 6.3) in Eventlet’s WSGI parser allowing HTTP Request Smuggling (bypass controls, cache poisoning, user targeting) has been found. It has been fixed within Eventlet 0.40.3. A security advisory has been published [7]. ## Call to Action That would be worth considering introducing small experiments as opportunities to identify or learn any weaknesses in new threading architectural models. That could start by preparing and performing some perf scale testing at your deliverables levels. That will help you to define the right scaling configuration for your deliverables. You can draw inspiration from Neutron's rally jobs [8] and from Ironic's scripting created for benchmark purposes [9]. More than a year ago, Dan sparked the performance testing topic idea [10], that's the right time to consider it more deeply. If you do not start the migration of your deliverables, I'd encourage you to plan and prioritize it as soon as possible. Time flies and the later your migration starts the harder it will be. Python 3.15 comes with its share of breaking changes [11] so I'd not suggest waiting for that time. If you are scheduling a PTG session on your side about Eventlet, then please let us know by updating the eventlet removal wiki page [12]. If your service is now migrated, I'd invite you to tag the launchpad bugs which were related to Eventlet, and, if it makes sense to close them. You are now entering a clean phase. ## Final Thoughts During Flamingo we observed tremendous progress, and we are now going straight toward the final release of Flamingo. The PTG, and Gazpacho that will be the logical continuation of the jobs already done. Flamingo will mark a significant release due to the fully migrated bricks and services. They will allow us to enter a beneficial feedback loop. The migration path is now well cleared by all the previous actions and changes applied into OpenStack. Postponing the beginning of the migration will make your life harder. We want to prevent this from happening to you. Your journey start here https://removal.eventlet.org/ If you need information join-us on the #openstack-eventlet-removal OFTC channel. Thanks to all the people who made this migration possible until now. Thanks for your attention. [1] https://ironicbaremetal.org/blog/coming-soon-threading/ [2] https://review.opendev.org/c/openstack/barbican/+/955301 [3] https://review.opendev.org/c/openstack/heat/+/952651 [4] https://docs.openstack.org/futurist/latest/reference/index.html#futurist.Dy… [5] https://docs.openstack.org/oslo.service/latest/user/backend.html [6] https://review.opendev.org/c/openstack/governance/+/952903 [7] https://github.com/advisories/GHSA-hw6f-rjfj-j7j7 [8] https://opendev.org/openstack/neutron/src/branch/master/rally-jobs [9] https://opendev.org/openstack/ironic/src/branch/master/tools/benchmark [10] https://review.opendev.org/c/openstack/governance/+/902585/comment/979db3f6… [11] https://docs.python.org/es/dev/whatsnew/3.15.html#threading [12] https://wiki.openstack.org/wiki/Eventlet-removal#Project-specific_events -- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[keystone][ops] Upgrade to 2025.1 and "corner cases"
by Dmitriy Rabotyagov 03 Sep '25

03 Sep '25

Hey folks, I wanted to raise awareness of operators regarding Keystone upgrade to Epoxy (2025.1), as found that existing release notes are slightly more vague about corner case definition. During analysis, it appeared that a lot of users (and under "a lot" I mean 4 figures number) in my really old deployments (which were deployed during Newton), still in use passwords hashed with sha512_crypt which has been dropped in 2025.1 [1]. As this was referenced as a "corner case" in upgrade docs, it may not bring enough attention to this matter reading notes, while sha512_crypt removal is mentioned in "Other" section which I personally missed when analyzing upgrade requirements. So I would highly recommend to ensure that all your users are using supported hashing algorithms before the upgrade to Epoxy, and inform them to reset their passwords if they don't. You can list users who are using unsupported hashing algorithm using following MySQL query: SELECT distinct l_u.user_id FROM keystone.local_user AS l_u JOIN keystone.password AS hash ON l_u.id = hash.local_user_id WHERE (hash.password_hash LIKE '$6$%' OR hash.password_hash LIKE '$5$%') AND hash.expires_at i s null; Hope this helps somebody to save some time in the future. [1] https://opendev.org/openstack/keystone/commit/4a4137d5f77ced3f4f011846fb9c2…

7 13

[Nova&Neutron] pagination returns an http, not https href link
by Chang Xue 03 Sep '25

03 Sep '25

Hello, we just migrated using new openstack CLI tools, and when using pagination for both Nova and Neutron, we noticed that they are returning http href link although they are expecting https, causing failure: ``` openstack port list Failure: Unable to establish connection to http://openstack....example.com:9696/v2.0/ports: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')). Retrying in 0.5s.1 retries left Unable to establish connection to http://openstack.....example.com:9696/v2.0/ports: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) ``` Is this a bug in Nova/Neutron? I tried other services like Heat, Keystone, etc, and they either returning https href links or just take relative path without schema/host. Thanks, Chang

3 10

[neutron][ovn] Logical Port Statistics
by James Denton 03 Sep '25

03 Sep '25

Hello all, Is anyone aware of a method to gather statistics (bytes in/out, packets, etc.) for logical router ports or similar when using ML2/OVN? I understand neutron-metering-agent parity is currently a feature gap, but I’m curious if there’s some OVN-native functionality that can provide those details. The ask is to provide a bytes-in/out counter for tenant routers, specifically on the external interface(s). Thanks, James Get Outlook for Mac <https://aka.ms/GetOutlookForMac>

3 3

[release][PTLs] Reminder to 2025.2 Flamingo Cycle highlights
by Elõd Illés 02 Sep '25

02 Sep '25

Hi, Let me remind you that this week is the week when 2025.2 Flamingo's Cycle highlights should be finalized (now that the Feature Freeze deadline has passed) so that they can be included in release marketing preparations. Thanks, Előd Illés irc: elodilles @ #openstack-release

1 0

[magnum] Proposing Scott Davidson as magnum-capi-helm core reviewer
by Michał Nasiadka 02 Sep '25

02 Sep '25

Hello, I’d like to propose Scott Davidson as a core reviewer for magnum-capi-helm repository. His insightful and timely reviews have been helping to drive fixes and new features - and it would be great to have him as part of the core reviewers team. Best regards, Michal Nasiadka

3 3

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.2/R-4)
by Goutham Pacha Ravi 02 Sep '25

02 Sep '25

Hello Stackers, We're in the final leg of our release journey with the 2025.2 "Flamingo" release [1]. Last week, we observed a feature freeze across all OpenStack deliverables that follow a "cycle-with-rc" [2] release model. Project teams are now preparing their release candidates, which will be posted next week. Polls have opened to elect a Project Team Lead in the Horizon (OpenStack Dashboard) project, as well as to elect four representatives on the OpenStack Technical Committee. Polls will close on September 17th, 2025, at 23:45 UTC [2]. Election officials observed that a good portion of the electorate would not receive their ballots because they haven't signed up to receive emails from the election system: CIVS. Please do ensure that your preferred email on gerrit has been used to opt in to CIVS emails. If you opt in newly, you will not receive an email ballot; instead, you'll see a pending poll invitation on CIVS: https://civs1.civs.us/cgi-bin/opt_in.pl In the past week, the Watcher project team has constituted a new set of project liaisons, and election officials have let the TC know that four OpenStack project teams have not had any PTL nominees. These are Monasca, OpenStack Charms, Venus, and Vitrage. We expect to make some changes shortly. === Weekly Meeting === The OpenStack Technical Committee had its last weekly meeting over IRC on August 26th, 2025 [3]. We had a lively discussion on several key topics. We're closing out the 'Migrate from WSGI scripts to module paths' goal [4] as complete. We also discussed the status of the Monasca project team [5]. It's still a point of contention with some folks wanting to move forward with its retirement while others want to give a new contributor a chance to get it running again. We've decided to defer a final decision to allow for more discussion on Gerrit and to give the new contributor a chance to make some progress. Another important topic we covered was the impact of the recent OIF membership renewals on the ongoing TC elections. With a significant number of potential voters not renewing their memberships, we are concerned about potential disenfranchisement. We hope to urge renewals past these elections and share a follow-up regarding the elections to the OIF Board. Finally, we discussed a proposed "phone-home" patch in the Cinder project [6]. While the feature technically sends data to an external storage system rather than an OpenStack service, there was a consensus that any "call-home" functionality should be opt-in, not enabled by default. This is a matter of respecting user privacy and not making assumptions about an operator's environment. Jon Bernard (jbernard) plans to draft a formal resolution to address this, and we'll advise on the process. The next meeting of the OpenStack TC is on Tuesday, September 2nd, 2025. This meeting will be hosted simultaneously on Meetpad (video) and IRC (#openstack-tc on OFTC) at 1700 UTC. Please find the agenda and call details on the meeting's wiki page [7]. I hope you'll be able to join us there! === Governance Proposals === ==== Merged ==== - Use DPL model for Watcher project leadership for 2026.1 release | https://review.opendev.org/c/openstack/governance/+/958085 ==== Open For Review ==== - Retire Metalsmith project from bare metal program | https://review.opendev.org/c/openstack/governance/+/958297 - Show inactive project status in project.yaml | https://review.opendev.org/c/openstack/governance/+/958229 - Retire Monasca project | https://review.opendev.org/c/openstack/governance/+/953671 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - Mark "Migrate from wsgi scripts" goal as completed | https://review.opendev.org/c/openstack/governance/+/958817 === Upcoming Events === - 2025-09-06: OpenInfra Days, Kenya: https://www.meetup.com/kenya-openinfra-user-group/ - 2025-09-17: OpenStack TC and Horizon project elections conclude: https://governance.openstack.org/election/ - 2025-09-09: OIF Board Monthly meeting: https://board.openinfra.org/ - 2025-10-01: OpenStack 2026.1 "Flamingo" release day - 2025-10-03: OpenStack's Birthday Meetup, Austin: https://www.meetup.com/openinfra-austin/events/310508680 - 2025-10-17: OpenInfra Summit, Paris-Saclay: https://summit2025.openinfra.org/ - 2025-10-27: OpenInfra PTG: https://openinfra.org/ptg/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.2 "Flamingo" Release Schedule: https://releases.openstack.org/flamingo/schedule.html [2] "cycle-with-rc" release model: https://releases.openstack.org/reference/release_models.html#cycle-with-rc [3] TC Meeting IRC Log, August 26th 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-08-26-17.00.html [4] Community Goal to update wsgi configuration: https://governance.openstack.org/tc/goals/proposed/migrate-from-wsgi-script… [5] Retiring the Monasca project team: https://review.opendev.org/c/openstack/governance/+/953671 [6] Cinder driver phoning home: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [7] TC Meeting Agenda, September 2nd, 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[neutron] Bug deputy report (week starting on August 25)
by Elvira Garcia Ruiz 01 Sep '25

01 Sep '25

Hi folks, Here you have the list of bugs reported for Neutron during last week. (Aug 25 - Aug 31) High ------- - https://bugs.launchpad.net/neutron/+bug/2121609 flake8 plugins from neutron-lib are enabled by default, breaking existing projects dependent on it Fix proposed by Takashi Kajinami https://review.opendev.org/c/openstack/neutron-lib/+/958786 - https://bugs.launchpad.net/neutron/+bug/2121649 [n-t-p] Test "test_subport_connectivity" failing randomly in 2025.1 Unassigned. Medium ----------- - https://bugs.launchpad.net/neutron/+bug/2121605 nova and neutron pagination returns an http, not https href link Unassigned Low ------ - https://bugs.launchpad.net/neutron/+bug/2121530 [SR-IOV] Trusted VF port MAC address can be changed from inside the VM Fix proposed by Ralonsoh https://review.opendev.org/c/openstack/neutron/+/958877 Undecided -------------- - https://bugs.launchpad.net/neutron/+bug/2121582 Source / Destination IP address is not respected in firewall group rule FWaaS v2 Unassigned. I will ask mlavalle about how to triage this since it’s ovs-fw related if I understand correctly. Best regards! Elvira

1 0