March 2026 - openstack-discuss - lists.openstack.org

[all][elections][ptl][barbican][horizon] PTL 2026.2 cycle Election Voting Last Days
by Ian Y. Choi 19 Mar '26

19 Mar '26

We are coming down to the last hours for voting in the Barbican, Horizon elections. Voting ends Mar 18, 2026 23:45 UTC. Search your Gerrit preferred email address[0] for the messages with subjects like... OpenStack 2026.2 Cycle - Barbican PTL Election Poll OpenStack 2026.2 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-election 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

[qa] Canceling today QA office hour
by Ghanshyam Maan 19 Mar '26

19 Mar '26

Due to another conflict, I will cancel today's office hour. The next office hours will be on 1st April. https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Details -gmaan

1 0

[cinder] festival of reviews friday 2026-03-20
by Brian Rosmaita 18 Mar '26

18 Mar '26

Hello Argonauts, It's already the third week of March, which means that the twice monthly Cinder Festival of Reviews will be held at the end of this week on Friday 20 March. who: Everyone! what: The Cinder Festival of Reviews when: Friday 20 March 2026 from 1400-1600 UTC where: videoconf info on the etherpad etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews This recurring meeting, that happens on the first and third Friday of each month, can be placed on your calendar by using this handy ICS file: https://meetings.opendev.org/calendars/cinder-festival-of-reviews.ics See you there!

1 0

March 17 Digital Sovereignty Meeting Recording & Plan Going Forward
by Kendall Nelson 18 Mar '26

18 Mar '26

Hello Everyone! Thank you to those who were able to attend yesterday's meeting. We really appreciate you taking time out of our day to support collaboration around OpenInfra and Digital Sovereignty. For those that were unable to attend, here is the recording! https://zoom.us/rec/share/5C87PC0AwqXFVCeW-f0ydLppVrEsUSuvRyV_M9xSgvPcVq7ZF… As always, please note in our etherpad <https://etherpad.opendev.org/p/Digital-Sovereignty-WG> that you have watched the recording and feel free to add your own notes as well. Just because you are not able to make it to all the meetings, doesn't mean you don't have valuable insight - we want to hear from you. Now, as to how our efforts are going - since we are in a good place with the landing page, link coming soon - we are going to take a few weeks to break into smaller groups to work on some of the deliverables and make our next big meeting during the PTG (April 20-24) with that exact timing TBD via a poll in a couple weeks. *If there is a particular deliverable (case studies, best practices, proprietary v openstack, and thought leadership blogs) please make sure to add your name to those sections (and email address to the attendees section) of the etherpad <https://etherpad.opendev.org/p/Digital-Sovereignty-WG> by the end of the week so I can set up individual threads for those subgroups. * Any questions? Please feel free to ask! -Kendall

1 0

[cinder][ops] Migrate volume backend from decommissioned node
by Isaac Vicente 18 Mar '26

18 Mar '26

Hello all, In the past week I've added a new controller and decommissioned an old one, following the official documentation [1], and I wrote a version of my own [2], specific to my environment. In the section "Removing existing controllers", it's necessary to move agents and remove services of the node that will be decommissioned. So far so good, until I realize that a volume has the following property: os-vol-host-attr:host: <old_node>@rbd-1#rbd-1 It means that this volume is still on the backend of the removed node. So I tried to migrate it to another backend, and the migration status is "starting" for a long time. In the cinder-scheduler logs: WARNING cinder.scheduler.host_manager volume service is down. (host: <old_node>@rbd-1) To me, the migration stays in this status because the proper backend is down. To mention, I'm using Ceph as cinder backend. Also, there's no mention of the volume being migrated on other controller nodes. Is there any method to migrate all volumes of this backend without needing to re-deploy the old controller? Versions: - Openstack: caracal (2024.1) - OS: Ubuntu 22.04 - kolla-ansible: 18.8.1 [1] https://docs.openstack.org/kolla-ansible/latest/user/adding-and-removing-ho… [2] https://isaacvicente.github.io/posts/replacing-control-nodes-with-kolla-ans…

3 4

[docs] Documentation sites are extremely slow
by Eugen Block 18 Mar '26

18 Mar '26

Hi, I'm not sure how long it has been like that, but when I tried to access the documentation yesterday, it took forever to load. And it is the same today, it takes several minutes to load any site, for example: https://docs.openstack.org/cinder/2025.2/admin/ I tried it from different networks, didn't make a difference. Is that a known issue? Thanks, Eugen

5 7

[dev][nova] Intel TDX support
by Anton Iacobaeus 18 Mar '26

18 Mar '26

Hi, I work with confidential computing and has previously contributed to Proxmox [1] to enable support for Intel TDX. I am looking to do the same for Openstack Nova. I have proposed a blueprint [2] and am drafting a spec with target for 2026.2 release. From what I gather, support for AMD SEV and SEV-ES is already implemented in Nova, while SEV-SNP support is ongoing. TDX shares some commonalities with SEV-SNP, and I believe that the work on both can be conducted in tandem. I also have experience with SEV-SNP and am happy to contribute if needed. Early feedback or any concerns and guidance are very welcome! [1] https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_9.1 [2] https://blueprints.launchpad.net/nova/+spec/intel-tdx-libvirt-support Best Regards, Anton

4 4

[Masakari] team meeting today at 07:00-08:00 UTC
by Sei Sano 18 Mar '26

18 Mar '26

Hi team Apologies for the short notice ― just a reminder that we have our regular team meeting today. When: 07:00 UTC, <day>, <date> Where: #openstack-masakari (OFTC) Agenda: https://etherpad.opendev.org/p/masakari-meeting-2026.1 If you have any topics to discuss, please add them to the agenda. Thanks, Sei Sano

5 8

[PTG 2026.2] Scheduled Time Slots for Ironic Sessions
by CID Onyedikachi 18 Mar '26

18 Mar '26

Hello Everyone! Ironic PTG sessions have been scheduled for Monday through Friday, 20 - 24 April, 13:00 - 17:00 UTC in the Mitaka room. If any slot doesn’t work for you, a different time can be arranged. Feel free to reply to this email if a change is needed. -Afonne-CID (cid)

2 1

[cinder][backup] BackupManager.restore_backup() missing 1 required positional argument: 'volume_is_new'
by Eugen Block 17 Mar '26

17 Mar '26

Hi, my environment is: Epoxy on Ubuntu 24.04 package-based installation I'm looking for some clarification regarding this bug report [0]. I don't really understand if it's fixed or not. I was trying to rollback a volume to its backup version when I got this stack trace: Backup service: cinder.backup.drivers.ceph.CephBackupDriver. 2026-03-17 08:37:02.805 1516544 ERROR oslo_messaging.rpc.server [None req-54d97a73-522d-411a-9982-1f6bb0ea905b 89c5dcc8793d4867bae22d50e51e16b3 90c403f317ee47feb0dad58461e76fb1 - - - -] Exception during message handling: TypeError: BackupManager.restore_backup() missing 1 required positional argument: 'volume_is_new' 2026-03-17 08:37:02.805 1516544 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2026-03-17 08:37:02.805 1516544 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/server.py", line 174, in _process_incoming 2026-03-17 08:37:02.805 1516544 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2026-03-17 08:37:02.805 1516544 ERROR oslo_messaging.rpc.server ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2026-03-17 08:37:02.805 1516544 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch 2026-03-17 08:37:02.805 1516544 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2026-03-17 08:37:02.805 1516544 ERROR oslo_messaging.rpc.server ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2026-03-17 08:37:02.805 1516544 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch 2026-03-17 08:37:02.805 1516544 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2026-03-17 08:37:02.805 1516544 ERROR oslo_messaging.rpc.server ^^^^^^^^^^^^^^^^^^^^^^ 2026-03-17 08:37:02.805 1516544 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/cinder/utils.py", line 1053, in wrapper 2026-03-17 08:37:02.805 1516544 ERROR oslo_messaging.rpc.server return func(self, *args, **kwargs) 2026-03-17 08:37:02.805 1516544 ERROR oslo_messaging.rpc.server ^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2026-03-17 08:37:02.805 1516544 ERROR oslo_messaging.rpc.server TypeError: BackupManager.restore_backup() missing 1 required positional argument: 'volume_is_new' It's stated that it was fixed in cinder versions 22 and 23, we are on Epoxy (cinder v 26) and still hit that issue. I then manually applied [1] which seems to have fixed the "volume_is_new" issue, at least I can restore volumes now. But I was also wondering why it took so long, and noticed that it doesn't keep the sparseness (although it should according to [2]. Here's the 'rbd du' output from a successfully restored volume: rbd du volumes-ssd/volume-6a9a8497-eacd-490e-be3e-f6dbdf638b5d NAME PROVISIONED USED volume-6a9a8497-eacd-490e-be3e-f6dbdf638b5d@backup.db61467a-5c29-4fca-b393-a1962dc6d2a8.snap.1773736256.760678 40 GiB 4.9 GiB volume-6a9a8497-eacd-490e-be3e-f6dbdf638b5d 40 GiB 40 GiB <TOTAL> 40 GiB 45 GiB I didn't expect that. Could anyone help me understand? Thanks! Eugen [0] https://bugs.launchpad.net/cinder/+bug/2025277 [1] https://review.opendev.org/c/openstack/cinder/+/914775 [2] https://bugs.launchpad.net/cinder/+bug/2007615

1 0