September 2025 - openstack-discuss

[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 8

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