- openstack-discuss - lists.openstack.org

[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 15 Sep '25

15 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 15 Sep '25

15 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 11 Sep '25

11 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 11 Sep '25

11 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 10 Sep '25

10 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 08 Sep '25

08 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 08 Sep '25

08 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