August 2025 - openstack-discuss - lists.openstack.org

Volume retype fails with Libvirt Nova - disk does not have active block job
by Karl Kloppenborg 14 Aug '25

14 Aug '25

Hi Openstackers. We’re currently migrating between storage backends and for the most part retype works correctly. However some VM’s fail the volume migration/retype quickly with the following error: Stack trace here: https://gist.github.com/inventionlabsSydney/40cd945685c798c489d729d2bcd5ec1e Has anyone else experienced this, we have tried looking around on the web and haven’t seen anything related to this. Much 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>

1 0

[horizon][cinder] service type block-storage not activated
by Eugen Block 14 Aug '25

14 Aug '25

Hi all, during further testing of my upgraded Epoxy cloud (before upgrading our production cloud) I noticed this error message in the browser console when analyzing the response times with the dev tools: > Possibly unhandled rejection: Diensttyp ist nicht aktiviert: block-storage "Diensttyp ist nicht aktiviert" translates to "service type is not activated". But looking at the service versions, there is an entry for "block-storage": root@controller01:~# openstack versions show | grep storage 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' | RegionOne | block-storage | 3.0 | CURRENT | https://controller.domain:8776/v3/ | 3.0 | 3.71 | I remembered this thread [0] and read it again, but I'm still insecure if I need to change anything or not. Our production cloud has been created around 10 years ago, so I'm pretty sure there are many legacy things one could clean up. But could anyone please clarify if something is missing here or not? Or is it a red herring in horizon? I'd really appreciate any pointers! Thanks! Eugen [0] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack…

1 2

[nova][elections][ptl] Application for the PTL role 2026.1
by René Ribaud 13 Aug '25

13 Aug '25

Hello, I am announcing my new candidacy for the PTL role for Nova and Placement. Serving as PTL in the Flamingo cycle was both a rewarding and instructive experience. It allowed me to learn the responsibilities and workload of the role, build stronger connections across the community, and help contributors move their work forward. In the next cycle, I want to continue fostering a welcoming and collaborative environment for all contributors. I will continue and improve our efforts to enhance bug triage, reduce the number of open bugs, and support timely reviews to help features progress toward completion. I am also eager to follow and participate in the Eventlet removal effort, which began in Flamingo and represents a major step for OpenStack. This is a particularly interesting challenge—not highly visible to most users, but crucial for the long-term health, performance, and maintainability of the project. My main focus, and the most important thing to me, will remain ensuring that Nova and Placement stay robust, maintainable, and aligned with our users’ needs. Thank you for your trust so far, I’d be happy to continue serving in this role. Thanks, René

1 0

[cinder] IBM SVf driver callhome
by Vivek Pandey 13 Aug '25

13 Aug '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 7

[publiccloud-sig] Public Cloud SIG meeting d.d. 13 August
by Kees Meijs | Nefos 12 Aug '25

12 Aug '25

Hello Stackers, On Wednesday 13 August 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 Since I'm vacationing during the meeting, I won't be joining myself. 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

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

12 Aug '25

Hello Stackers, We're two weeks away from a feature freeze across all projects following a "cycle-with-rc" release model [1]. This is a significant release milestone, and OpenStack project teams are hard at work on code review iterations to meet this deadline. In the past week, we kicked off elections for the next crop of OpenStack Project Team Leads as well as for four seats on the OpenStack Technical Committee [2]. These leadership positions are voluntary and form the bedrock of our community's principle of "Open Community" [3]. There is a long tradition of mentoring contributors to take on these important roles, and each comes with a unique opportunity to learn, impact OpenStack software, and give back to the community. If you're considering nominating yourself but need assistance, please do not hesitate to pop into #openstack-tc on OFTC and ask questions. The nomination period closes on August 20th. As far as governance updates are concerned, the OpenStack TC defined affiliation diversity within its charter and began the process of affirming liaisons for various projects following the "distributed project leadership" model of governance [4]. We also began the process of retiring the Monasca project team and its various deliverables. I'll keep you posted on the progress in the coming weeks. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee was held simultaneously on Meetpad [5] and IRC [6]. Attendance was low due to summer break in various parts of the northern hemisphere where members hail from. We discussed how the Monasca retirement process will proceed. We also discussed the runtime update for the 2026.1 "Gazpacho" release, specifically the Python version to be supported. Debian 13 (Trixie) is set to release with Python 3.13, which is a key factor in our decision-making. Initial smoke tests on a Trixie devstack-integration test job appear promising. We addressed some concerns regarding the TC charter change regarding organizational affiliation. We also reviewed the gate's health, with recent reports of Debian job failures attributed to stale mirrors and cluster maintenance. We discussed the progress on the SRBAC community goal. There are several projects that have not yet completed Phase 1. We'll be following up on this during this week. We reminded folks that the OpenStack User Survey for 2025 is open and will close at the end of this month [7]. Please take the survey and spread the word. OpenStack project teams would appreciate feedback through the survey, and we are looking to discuss the results at the PTG in October. The next meeting of the TC is today, August 12, 2025, at 1700 UTC. This meeting will be hosted simultaneously over IRC, in OFTC's #openstack-tc channel. Please find the meeting's agenda in the wiki [8]. I hope you'll be able to join us. === Governance Proposals === ==== Merged ==== - Define "affiliation" within the context of the TC | https://review.opendev.org/c/openstack/governance/+/956024 - Add Extra ACs for governance repositories | https://review.opendev.org/c/openstack/governance/+/956836 - os-test-images never releases | https://review.opendev.org/c/openstack/governance/+/954249 - Add series names to runtimes doc | https://review.opendev.org/c/openstack/governance/+/955810 - Fix project_stats_check script | https://review.opendev.org/c/openstack/governance/+/955108 ==== Open for review ==== - Reset freezer project leadership from DPL back to PTL | https://review.opendev.org/c/openstack/governance/+/956918 - Reset oslo project leadership from DPL back to PTL | https://review.opendev.org/c/openstack/governance/+/956912 - Freezer - remove information about Disaster Recovery | https://review.opendev.org/c/openstack/governance/+/941893 - Reset Release Management project leadership from DPL back to PTL | https://review.opendev.org/c/openstack/governance/+/956916 - Reset watcher project leadership from DPL back to PTL | https://review.opendev.org/c/openstack/governance/+/956913 - Reset requirements project leadership from DPL back to PTL | https://review.opendev.org/c/openstack/governance/+/956915 - Remove Monasca from active project | https://review.opendev.org/c/openstack/governance/+/953671 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 === Upcoming Events === - 2025-08-20: Nominations close for OpenStack elections - 2025-08-26: OpenInfra Days, Korea: https://2025.openinfradays.kr/ - 2025-08-28: Feature Freeze deadline, Milestone-3 of the Flamingo release [1] - 2025-08-29: Colombia OpenInfra User Group Meetup: https://www.meetup.com/colombia-openinfra-user-group/events/307096751/ - 2025-10-17: OpenInfra Summit, Paris-Saclay: https://summit2025.openinfra.org/ === 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 [8]. 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] 2026.1 OpenStack Elections: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] Open Community: https://openinfra.org/four-opens/open-community/ [4] Refreshing liaisons for DPL projects: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [5] TC Meeting Video Recording, Aug 5, 2025: https://youtu.be/e5LPZNjdIzM [6] TC Meeting IRC Log, Aug 5, 2025: https://meetings.opendev.org/meetings/tc/2025/tc.2025-08-05-17.00.html [7] Take the 2025 OpenStack User Survey: https://www.openstack.org/user-survey [8] TC Meeting Agenda, Aug 12, 2025: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[tc][freezer][watcher][release][requirement][oslo][ironic] projects need to refresh the DPL model for the next cycle
by Ghanshyam Maan 11 Aug '25

11 Aug '25

Hi All, As you know, we have six projects (listed below) in the DPL model. As per process[1], we need to reset the DPL model every cycle. The project team either needs to opt-in to the DPL model by -1 from all currently listed liaisons (refer to the document for exact steps[1]) or plan for the PTL election. 1. Freezer: https://review.opendev.org/c/openstack/governance/+/956918 2. Watcher: https://review.opendev.org/c/openstack/governance/+/956913 3. Release: https://review.opendev.org/c/openstack/governance/+/956916 4. Requirement: https://review.opendev.org/c/openstack/governance/+/956915 5. Oslo: https://review.opendev.org/c/openstack/governance/+/956912 6. Ironic: https://review.opendev.org/c/openstack/governance/+/956917 [1] https://governance.openstack.org/tc/reference/distributed-project-leadershi… -gmaan

3 3

[tacker] Cancel weekly meeting on August 11th
by Yasufumi Ogawa 11 Aug '25

11 Aug '25

Hi team, Due to summer vacation, I'm going to cancel the IRC meeting this week. Thanks, Yasufumi

1 0

Inquiry: Integrating Tungsten Fabric with Neutron in Kolla Ansible 2023.1
by Thamanna Farhath 08 Aug '25

08 Aug '25

Hello OpenStack Community, We are currently using OpenStack Kolla Ansible (2023.1 release). As part of our networking design, we are evaluating the possibility of integrating Tungsten Fabric (TF) with Neutron. I would like to clarify the following points: Compatibility – Does the Kolla Ansible 2023.1 version officially support integration with Tungsten Fabric? Reference Material – If supported, could you please suggest any official documentation, blogs, or reference implementations that describe the integration process? Integration Guidance – What would be the recommended approach for integrating TF with Neutron in a Kolla-based deployment? Are there any specific configuration patterns or community best practices we should follow? Necessity – In the context of building a public cloud, is Tungsten Fabric integration considered mandatory for production-grade networking, or can similar functionality be achieved with the default Neutron backends (e.g., OVN/OVS)? We are currently at the early stages of our deployment plan and can make architectural changes before the release. Any guidance, experiences, or resources from the community will be highly valuable for our decision-making process. Thank you in advance for your support. 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

[release] Release countdown for week R-7
by Thierry Carrez 08 Aug '25

08 Aug '25

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

1 0