June 2025 - openstack-discuss - lists.openstack.org

[cinder] Unexpected Ceph RBD snapshot retention behavior when deleting image-based volumes
by Rocha Lobo, Vinicius 18 Jun '25

18 Jun '25

Hi, OpenStack Community. I'm part of the StarlingX Community and our starlingx-openstack distribution is currently delivering the 2024.1 (Caracal) release. We are facing an issue when using Cinder with the Ceph RBD backend: volumes created from Glance images leave behind protected snapshots and *.deleted volumes in the cinder-volumes pool after deletion, and these remnants are not being cleaned up automatically, even though I’ve enabled deferred deletion and garbage collection. So, I'm writing this email to explain our current issue and get feedback on this new Launchpad [1] I’m creating for Cinder. Environment: * OpenStack version: 2024.1 (Caracal) * Ceph version: Reef * Cinder configuration (via Helm override): conf: cinder: backend_defaults: rbd_flatten_volume_from_snapshot: True enable_deferred_deletion: True deferred_deletion_purge_interval: 10 ceph: image_volume_cache_enabled: False Issue description: 1) Create volume(s) from an image: * openstack volume create --image <image_id> --size 100 volume-test 2) Cinder creates a protected snapshot of the source image and then clones from it (as expected due to Ceph’s requirement for protected snapshots when cloning). 3) Delete the volume(s) via OpenStack CLI: * openstack volume delete volume-test After the deletion the corresponding RBD image and its snapshot are not cleaned up: * rbd -p cinder-volumes ls -l NAME SIZE PARENT FMT PROT LOCK <uuid>.deleted 100 GiB 2 <uuid>.deleted@<clone_snap>.clone_snap 1 GiB 2 yes... Even with the garbage collection features enabled (enable_deferred_deletion, rbd_flatten_volume_from_snapshot, and deferred_deletion_purge_interval), these protected snapshots and deleted volumes persist indefinitely, unless I clean them manually: * rbd snap unprotect <volume>.deleted@<snapshot> -p cinder-volumes * rbd snap rm <volume>.deleted@<snapshot> -p cinder-volumes * rbd rm <volume>.deleted -p cinder-volumes Here’s the logs that cinder pod shows while trying to delete the volume each 10 seconds: 2025-05-28 19:44:48.079 8 INFO cinder.volume.drivers.rbd [-] Purging trash for backend 'ceph-store' 2025-05-28 19:44:58.076 8 INFO cinder.volume.drivers.rbd [-] Purging trash for backend 'ceph-store' 2025-05-28 19:45:08.081 8 INFO cinder.volume.drivers.rbd [-] Purging trash for backend 'ceph-store' Questions: * Is this behavior expected in Cinder/CEPH integrations? * Shouldn't Cinder unprotect/delete the snapshot when the last volume, depending on how it is removed? Any insights or best practices would be greatly appreciated. Thanks in advance, Vinicius Lobo StarlingX contributor [1] https://bugs.launchpad.net/cinder/+bug/2114853

2 1

[all][tc][cyborg] Call for cyborg project maintainers
by Ghanshyam Maan 18 Jun '25

18 Jun '25

Hello Everyone, Cyborg project is lacking the active maintenance. The gate is broken, no response on the fix[1]. Two weeks ago, Sean raised the conern to ML[2] but there is no response from current core. We discussed it in TC meeting (last week[3] and today[4]) and as per foundation staff reachout, the next step is to call for new maintainers. If anyone using or interested to maintain it then this is right time to step up. Also, I would like existing maintainers (first of all, thanks for maintaining it till now) to give more insight about project status and their bandwidth which can help new maintainers to onboard. As per TC process to check project status, I have proposed to mark cyborg as inactive[5], feel free to provide your opinion here or in gerrit. If we do not hear back and mark project Inactive, there will be no cyborg project deliverables release in this cycle. [1] https://review.opendev.org/c/openstack/cyborg/+/949772 [2] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] https://meetings.opendev.org/meetings/tc/2025/tc.2025-06-10-17.00.log.html#… [4] https://meetings.opendev.org/meetings/tc/2025/tc.2025-06-17-17.00.log.html#… [5] https://review.opendev.org/c/openstack/governance/+/952798 -gmaan

1 0

Nova bug report #2114855
by Vicentini Fracarolli, Joao 17 Jun '25

17 Jun '25

Hello OpenStack Community, I'm part of the StarlingX Community and our starlingx-openstack distribution is currently delivering the 2024.1 (Caracal) release. We were exploring the openstack-client "server rebuild" feature [1], and we might have found a bug. So, I'm writing this email to explain our current issue and get feedback on this new Launchpad we are creating for the Nova component https://bugs.launchpad.net/nova/+bug/2114855 [2]. It happened in the following scenario: * Create a VM with some small disk flavor and a small image. For example, using a flavor of 1 GB with the Cirros image (~ 21 MB of disk size). * Try to rebuild the VM using a new image. Example: the ubuntu-jammy qcow image. When the steps above are executed with an image with a disk size greater than the flavor size, the Nova API returns an error and the VM is not rebuilt: Flavor's disk is too small for requested image. Flavor disk is 1073741824 bytes, image is 1283063808 bytes. (HTTP 400) (Request-ID: req-7db974bb-15f3-425f-b97b-98b789b7e10f) But when we use an image with a disk size smaller than the flavor disk size, but with a virtual size bigger than the flavor disk size, Nova will try to rebuild the VM and fail: the VM state will be ERROR. It looks like the Nova API is accepting such rebuild requests, but when Nova Compute checks for virtual size, it fails. Is that expected behavior? Shouldn't the Nova API reject the request with an explicit warning telling the user to resize the VM before trying to rebuild? Thank you very much [1] https://docs.openstack.org/python-openstackclient/latest/cli/command-object… [2]https://bugs.launchpad.net/nova/+bug/2114855 Bug #2114855 “VM rebuild starts even if image virtual size is gr...” : Bugs : OpenStack Compute (nova)<https://bugs.launchpad.net/nova/+bug/2114855> Description =========== Openstackclient + Nova API accept to rebuild server with virtual size greater than the specified flavor’s disk size. Steps to Reproduce ================== 1 - Create a server specifying a flavor with small disk size (example: 1 GB) and an image small enough to fit. openstack flavor create --ram 512 --disk 1 --vcpus 1 tiny openstack server create –flavor tiny –image cirros vm-test 2 - Try to rebuild the server using a larger image but that still fits. It’s v... bugs.launchpad.net

2 1

[nova] multiple pci types with same address
by Arnaud Morin 17 Jun '25

17 Jun '25

Hello nova team, Quick question regarding support for multiple types (see [1]) with the same address: {vendor_id: "10de", product_id: "233b", "address": "00000000:03:00.0", "resource_class": "CUSTOM_H200_A"} {vendor_id: "10de", product_id: "233b", "address": "00000000:04:00.0", "resource_class": "CUSTOM_H200_A"} {vendor_id: "10de", product_id: "233b", "address": "00000000:44:00.0", "resource_class": "CUSTOM_H200_A"} {vendor_id: "10de", product_id: "233b", "address": "00000000:45:00.0", "resource_class": "CUSTOM_H200_A"} {vendor_id: "10de", product_id: "233b", "address": "00000000:83:00.0", "resource_class": "CUSTOM_H200_B"} {vendor_id: "10de", product_id: "233b", "address": "00000000:84:00.0", "resource_class": "CUSTOM_H200_B"} {vendor_id: "10de", product_id: "233b", "address": "00000000:C3:00.0", "resource_class": "CUSTOM_H200_B"} {vendor_id: "10de", product_id: "233b", "address": "00000000:C4:00.0", "resource_class": "CUSTOM_H200_B"} This works fine, I was able to define multiple aliases: {name: "h200a", device_type:"type-PF", resource_class: "CUSTOM_H200_A"} {name: "h200b", device_type:"type-PF", resource_class: "CUSTOM_H200_B"} I did that to create two blocks of 4 resources (A or B). But now, I need to create a flavor to boot instances with these devices. I want to have only one flavor that can use either A or B: For now I created a flavor with: pci_passthrough:alias='h200a:4' And was forced to create a second flavor with h200b:4. Is there any way to achieve a single flavor with both: Something like this? pci_passthrough:alias='h200a:4|h200b:4' I can't figure that out for now, is it possible? [1] https://docs.openstack.org/nova/latest/admin/pci-passthrough.html#support-f…

2 1

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

17 Jun '25

Hello Stackers, We're fifteen weeks away from the coordinated 2025.2 "Flamingo" release of OpenStack [1]. Milestone-2 is in a couple of weeks. This milestone is observed by several project teams for bug targeting. From the point of view of OpenStack's governance, this milestone serves as a point where we vet project deliverables to be included in the coordinated release. Releases are not tagged for deliverables from project teams that are deemed "inactive" [2]. In OpenStack, a project team is considered "inactive" when it no longer has regular contributor engagement or ongoing development. This often reflects that the problem the project once addressed is now being solved more effectively by another solution—either within or outside OpenStack. Inactivity isn't a failure, but rather a natural sign of how technology needs evolve over time. Any community member can propose a change to mark a project team inactive prior to Milestone-2. Doing so will prevent shipping broken or unmaintained code. In the past week, the OpenStack Technical Committee did not make any new governance changes. The team's focus has been on the implementation of the DCO by our deadline of 2025-07-01. I'd like to gently remind you that beyond July 1st, changes without a "Signed-off-by" line in the commit message cannot be uploaded to Gerrit. If you have a project team meeting before this date, please let folks know about this change. === Weekly Meeting === The last weekly meeting of the TC was held over IRC on OFTC's #openstack-tc channel on Tuesday, 2025-06-10 [3]. The main focus of the meeting was tracking all the changes necessary for enforcing the Developer Certificate of Origin in lieu of the ICLA beginning on 2025-07-01 [4]. We noted changes to various infrastructure pieces, and while we're hoping for a smooth transition, we do anticipate some hiccups. We are hoping for the community's patience and cooperation as we iron out the kinks. Further, concerns were raised about the Cyborg project's apparent inactivity. The last change merged into Cyborg was over two months ago, and a critical CI fix remains open, lacking review attention. Efforts to engage the team via the mailing list have not yielded any response, and there is no recent activity on IRC or Gerrit. While it's known that the Cyborg team has historically preferred WeChat/Weixin for communication, relying on unofficial channels or Foundation staff for outreach isn’t sustainable. The TC agreed that it’s important to determine whether the project is defunct or simply in need of new leadership, and to encourage maintainers to monitor and respond through community channels. Additionally, a self-report from the Vitrage team indicated that Tempest tests are currently failing due to a lack of contributor time this cycle. With the M-2 milestone deadline approaching on July 3rd, we emphasized the importance of project teams providing accurate and timely updates to the release team. The next meeting of the OpenStack TC is today, 2025-06-17. It'll be held over IRC in OFTC's #openstack-tc channel at 1700 UTC. Please find the agenda on the meeting's wiki page [5]. I hope you'll be able to join us. === Governance Proposals === ==== Open for review ==== - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 === Upcoming Events === - 2025-07-03: OpenStack's 15th Birthday, Colombia User Group: https://www.meetup.com/colombia-openinfra-user-group/events/308383244 - 2025-06-28: OpenInfra+Cloud Native Day, Vietnam: https://www.vietopeninfra.org/void2025 - 2025-07-19: OpenInfra Days, Indonesia: https://2025.openinfra.id/ === 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. - IRC: Ping us using the tc-members keyword on the #openstack-tc IRC channel on OFTC. - Meeting: Join us at our weekly meeting. The Technical Committee meets every week on Tuesdays at 1700 UTC [4]. 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] Inactive projects: https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [3] TC Meeting IRC Log 2025-06-10: https://meetings.opendev.org/meetings/tc/2025/tc.2025-06-10-17.00.html [4] Replace ICLA with DCO: https://governance.openstack.org/tc/resolutions/20250520-replace-the-cla-wi… [5] TC Meeting Agenda, 2025-06-17: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

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

16 Jun '25

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

2 10

[neutron] bug deputy report for week of 2025-06-09
by Bence Romsics 16 Jun '25

16 Jun '25

Hi Team, We only had a handful of new bug reports last week: High: * https://bugs.launchpad.net/neutron/+bug/2113861 [FT] Test ``test_initialize_network_segment_range_support_parallel_execution`` randomly failing already unblocked on master, backport in progress: https://review.opendev.org/q/topic:bug/2113861 Medium: * https://bugs.launchpad.net/neutron/+bug/2114176 [L3] L3 agent ``ProcessMonitor`` is not correctly registering the new processes fix merged: https://review.opendev.org/c/openstack/neutron/+/952450 Low: * https://bugs.launchpad.net/neutron/+bug/2114190 [whitebox-neutron-tempest-plugin] ``test_only_dropped_traffic_logged`` test failing with the WSGI Neutron API migration fix merged: https://review.opendev.org/c/x/whitebox-neutron-tempest-plugin/+/951264 [BTW: Maybe this project would be in a better place under the openstack namespace?] RFE: * https://bugs.launchpad.net/neutron/+bug/2114451 [RFE] ports should contain a reference to the segment_id they are bound to Related to https://bugs.launchpad.net/neutron/+bug/2105855. Probably a good idea to discuss on the drivers meeting. Cheers, Bence

1 0

[nova] Is It Possible to Attach a Cinder Volume as device='lun' ?
by Janaka Wickramasinghe 16 Jun '25

16 Jun '25

Hi, I'm running an OpenStack setup with Fibre Channel (FC) storage using Cinder volumes. I'm currently trying to configure a Windows Failover Cluster in guest VMs and have encountered an issue. Windows is querying the SCSI device for the Device Identification VPD (Page 0x83). The LUN is attached as a SCSI device using a virtio-scsi controller. In the domain XML (via libvirt), I see that the disk is defined as <disk type='block' device='disk'> also has a <serial>cinder-vol-uuid</serial> When Page 0x83 is queried, it returns the serial value (i.e., the cinder-vol-uuid), which Windows fails to recognize or accept. However, if I modify the XML to use: <disk type='block' device='lun'> and remove the <serial> tag, the guest is able to retrieve the expected information (I had to stop the compute service and restart the libvirt domain). Unfortunately, any changes made directly to the domain XML do not persist. Is there a supported way to specify device='lun' instead of device='disk' for volumes attached ? Any guidance would be greatly appreciated. Thank you With Best regards, Janaka

3 3

Re: [Octavia] - Loadbalancer appear offline but are running
by Wells, Aaron 14 Jun '25

14 Jun '25

Hi Karl, We ran into and fixed this issue on our installation by making sure that the UDP heartbeat packets on port 5555 were reaching the controllers. Thanks. Aaron -- Aaron Wells wellsaar(a)iu.edu DevOps Engineer Jetstream 2 https://kb.iu.edu/d/bfde

2 1

[neutron] Neutron BGP integration upstream sync
by Jakub Libosvar 13 Jun '25

13 Jun '25

Hi all, as per the previous suggestions I created the doodle [1] to pick the right time when we could meet. Finding a good timeslot is challenging as I noticed interest from all around the globe (US, EU, Australia). Please vote for which slot fits you best and if anyone has better suggestions, please let me know and let’s discuss. Thanks! Jakub [1] https://doodle.com/group-poll/participate/aK9Nkknd/vote

1 1

[horizon] Cancel weekly meeting on 2025-06-18
by Tatiana Ovchinnikova 13 Jun '25

13 Jun '25

Hello team, I am cancelling the upcoming weekly meeting since most of the members are on PTO. See you all in two weeks, June 25th! With kind regards, Tatiana

1 0

[nova][eventlet-removal]Weekly sync video call
by Balazs Gibizer 13 Jun '25

13 Jun '25

Hi, The Nova core team agreed to have a weekly high bandwidth sync meeting about the ongoing Eventlet removal work. Here are the details: [public]Nova Eventlet removal sync Every Wednesday: 14:30-15:00 UTC (16:30 – 17:00 CEST) Video call link: https://meet.google.com/bcy-uqoz-hje Cheers, gibi

2 1

[neutron] Drivers meeting agenda for Friday, June 13th
by Brian Haley 12 Jun '25

12 Jun '25

Hello Neutrinos: We have one item on the agenda for tomorrow's drivers meeting. Please add anything else to the wiki [0] to discuss if I missed something. * [RFE] Internal DNS resolution with OVS Agent - https://bugs.launchpad.net/neutron/+bug/2112446 See you tomorrow, -Brian [0] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[designate] It only syncs at reboot
by Alexander Luedtke 12 Jun '25

12 Jun '25

Hello Everyone, I have a strange problem, I wanted the designate services as hidden master, everything works fine, expect that the designate server does only sync with the master DNS server if I do a reboot of the host where the designate docker is on, or I have to restart the designate docker. Has anyone an idea how to fix that ? best regards Alex

2 1

[horizon] Changing the Term “Instance” to “Server” for improved clarity and consistency
by Dmitriy Chubinidze 11 Jun '25

11 Jun '25

Propose changing the term "Instance" to "Server" ( "Instances" to "Servers") in the platform’s user interface. This update will be aiming to improve clarity for users, align with industry terminology, and create a more intuitive experience. "Server" is a more commonly understood term than "Instance", especially for users who are not deeply familiar with cloud computing. Major platforms like AWS and Azure often use "Server" in their UI, even when referring to virtual instances. Adopting this term will make OpenStack easier to use and understand. This change will affect only the visual elements — such as UI labels, menus, and documentation. The underlying code, APIs, and data structures using the term instance will remain unchanged. This ensures there is no impact on functionality or development processes. We are open to feedback and discussion on this proposal.

7 8

Re: Api routes
by Bernd Bausch 11 Jun '25

11 Jun '25

I took the liberty to add the OpenStack mailing list on CC. As far as I know, the list of a service's APIs is not advertised to users, except in the documentation. An operator with access to the cloud controllers can list all endpoints of a service by generating a policy file, for example oslopolicy-sample-generator --namespace nova This will create a YAML file that contains a paragraph similar to the following per endpoint, which describes the authorization policy of this endpoint: # Delete a server # DELETE /servers/{server_id} # Intended scope(s): project #"os_compute_api:servers:delete": "rule:project_member_or_admin" This example is from https://docs.openstack.org/nova/2025.1/configuration/sample-policy.html. You need to run the oslopolicy command on a controller that contains the service's (in this case, Nova's) code. ________________________________________ From: engineer2024 <engineerlinux2024(a)gmail.com> Sent: Tuesday, June 10, 2025 10:55 PM To: Bernd Bausch <berndbausch(a)gmail.com> Subject: Re: Api routes This is not what I need. I need a way, sya, for nova api services, how many api routes or urls it supports. like, /servers , /servers/detail/ /os-aggregates etc On Tue, Jun 10, 2025 at 1:41 PM Bernd Bausch <berndbausch(a)gmail.com> wrote: These commands list API endpoints in your cloud: openstack endpoint list openstack catalog list ________________________________________ From: engineer2024 <engineerlinux2024(a)gmail.com> Sent: Monday, June 9, 2025 2:59 PM To: openstack-discuss <openstack-discuss(a)lists.openstack.org> Subject: Api routes In openstack, is there a feature to list all the available routes for the rest api servers, instead of checking and referring the documentation? Thanks elinux

1 0

[openstack helm] [Glance] Glance showing OSError: unable to receive chunked part when uploading image
by daniel890723＠gmail.com 10 Jun '25

10 Jun '25

Hello i'm testing using Openstack-helm to install all component but after the installation complete i can't upload the OS image through both openstack CLI or Horizon it stuck at Queueing and when i checking Glance Api log it shows 2024-11-07 07:31:19.362 7 INFO glance.api.v2.image_data [None req-2bd28444-196c-42e9-94ef-18443b58310e b39b42e27f8646acad1303711f1dc8b8 e4ab1a6192b9486da698efa311086c53 - - default default] Unable to create trust: no such option collect_timing in group [keystone_authtoken] Use the existing user token. 2024-11-07 07:31:19.400 7 ERROR glance.api.v2.image_data [None req-2bd28444-196c-42e9-94ef-18443b58310e b39b42e27f8646acad1303711f1dc8b8 e4ab1a6192b9486da698efa311086c53 - - default default] Failed to upload image data due to internal error: OSError: unable to receive chunked part 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi [None req-2bd28444-196c-42e9-94ef-18443b58310e b39b42e27f8646acad1303711f1dc8b8 e4ab1a6192b9486da698efa311086c53 - - default default] Caught error: unable to receive chunked part: OSError: unable to receive chunked part 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi Traceback (most recent call last): 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/wsgi.py", line 1302, in __call__ 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi action_result = self.dispatch(self.controller, action, 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/wsgi.py", line 1345, in dispatch 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return method(*args, **kwargs) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/utils.py", line 415, in wrapped 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return func(self, req, *args, **kwargs) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/api/v2/image_data.py", line 299, in upload 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi with excutils.save_and_reraise_exception(): 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.force_reraise() 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi raise self.value 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/api/v2/image_data.py", line 162, in upload 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi image.set_data(data, size, backend=backend) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/notifier.py", line 492, in set_data 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi with excutils.save_and_reraise_exception(): 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.force_reraise() 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi raise self.value 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/notifier.py", line 443, in set_data 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.repo.set_data(data, size, backend=backend, 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/quota/__init__.py", line 322, in set_data 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self.image.set_data(data, size=size, backend=backend, 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/location.py", line 596, in set_data 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi self._upload_to_store(data, verifier, backend, size) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/location.py", line 487, in _upload_to_store 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi multihash, loc_meta) = self.store_api.add_with_multihash( 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/multi_backend.py", line 397, in add_with_multihash 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return store_add_to_backend_with_multihash( 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/multi_backend.py", line 479, in store_add_to_backend_with_multihash 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi (location, size, checksum, multihash, metadata) = store.add( 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/driver.py", line 294, in add_adapter 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi metadata_dict) = store_add_fun(*args, **kwargs) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/capabilities.py", line 176, in op_checker 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi return store_op_fun(store, *args, **kwargs) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/_drivers/filesystem.py", line 764, in add 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi raise errors.get(e.errno, e) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/_drivers/filesystem.py", line 746, in add 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi for buf in utils.chunkreadable(image_file, 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance_store/common/utils.py", line 73, in chunkiter 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi chunk = fp.read(chunk_size) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/utils.py", line 294, in read 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi result = self.data.read(i) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/utils.py", line 121, in readfn 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi result = fd.read(*args) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/format_inspector.py", line 956, in read 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi chunk = self._source.read(size) 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi File "/var/lib/openstack/lib/python3.10/site-packages/glance/common/wsgi.py", line 1045, in read 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi data = uwsgi.chunked_read() 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi OSError: unable to receive chunked part 2024-11-07 07:31:19.426 7 ERROR glance.common.wsgi Ceph Cluster Status: NAME DATADIRHOSTPATH MONCOUNT AGE PHASE MESSAGE HEALTH EXTERNAL FSID ceph /var/lib/rook 3 82m Ready Cluster created successfully HEALTH_OK 5cf8b9bb-13e1-4c31-b47d-9e7d92c3c05d Ceph osd status: ID CLASS WEIGHT REWEIGHT SIZE RAW USE DATA OMAP META AVAIL %USE VAR PGS STATUS TYPE NAME -1 0.35156 - 360 GiB 3.3 GiB 493 MiB 0 B 2.8 GiB 357 GiB 0.91 1.00 - root default -5 0.11719 - 120 GiB 1.1 GiB 164 MiB 0 B 964 MiB 119 GiB 0.92 1.01 - host instance-lu-1 2 hdd 0.11719 1.00000 120 GiB 1.1 GiB 164 MiB 0 B 964 MiB 119 GiB 0.92 1.01 195 up osd.2 -3 0.11719 - 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 - host instance-lu-2 0 hdd 0.11719 1.00000 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 195 up osd.0 -7 0.11719 - 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 - host instance-lu-3 1 hdd 0.11719 1.00000 120 GiB 1.1 GiB 164 MiB 0 B 951 MiB 119 GiB 0.91 1.00 197 up osd.1 TOTAL 360 GiB 3.3 GiB 493 MiB 0 B 2.8 GiB 357 GiB 0.91 MIN/MAX VAR: 1.00/1.01 STDDEV: 0.01 now i'm able to create Empty Volume using horizon(can't create volume using default cirros image ) and i can start an Instance without volume and mount the empty volume in(Ceph also can detect when i use that volume) is there something i need to set when starting glance? because i'm following the Openstack-helm installation document to install openstack with helm

4 7

nova.conf : can [pci]alias be multivalued ?
by Michel Jouvin 10 Jun '25

10 Jun '25

Hi, We need to support several GPU models in our Nova configuration. This normally requires to add multiple `alias` entries (lines) in the [pci] section of nova.conf. Unfortunately for us, it complicates a lot the generation of nova.conf by our system configuration management tool (where the section is represented by a dict/hash, meaning that there is only 1 possible entry for 'alias'). Before trying to hack our tool, we were wondering if there is a way to put the different values as a list for a single 'alias' line and what should be the separator or syntax ? I was not able to identify a generic description of the syntax for multivalued parameters, if there is a generic rule. I already found this limitation (but we could live with it) for Keystone [federation]trusted_dashboard for example... Thanks in advance for any hint. Best regards, Michel

4 6

[neutron] Bug deputy report for week of June 2nd
by Brian Haley 10 Jun '25

10 Jun '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/2112314 - [OVN] Missing call to update the 'neutron:ovn-bridge' in the OVN agent "metadata" extension - https://review.opendev.org/c/openstack/neutron/+/951512 * https://bugs.launchpad.net/neutron/+bug/2112569 - [ml2/ovn] Neutron sending network-vif-plugged event to nova on port down - https://review.opendev.org/c/openstack/neutron/+/951863 * https://bugs.launchpad.net/neutron/+bug/2112648 - [OVS Firewall] Remote-group member flows not restored after port rebind with same IP/MAC during migration to OVS - Patch included in bug - Need to reproduce Medium ------ * https://bugs.launchpad.net/neutron/+bug/2112453 - subnet create with subnet-pool and --gateway none creates gateway ip - Confirmed, needs owner * https://bugs.launchpad.net/neutron/+bug/2112492 - neutron-metadata-agent shows XXX (dead) status despite being functional in Neutron 26.0.0 - I could not confirm, asked for more info * https://bugs.launchpad.net/neutron/+bug/2112620 - [neutron-tempest-plugin] Test ``test_vlan_transparent_allowed_address_pairs`` failing - https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/952177 - Is more work necessary? Low --- * None Wishlist -------- * https://bugs.launchpad.net/neutron/+bug/2112313 - [OVN] Deprecate OVN metadata agent in favor of OVN agent (with metadata extension) - Rodolfo took ownership * https://bugs.launchpad.net/neutron/+bug/2112446 - [RFE] Internal DNS resolution with OVS Agent - Will add to future driver's agenda

1 0

[CINDER] Dependent reviews need to be merged
by Harsh Ailani 10 Jun '25

10 Jun '25

Hello core reviewers, The following reviews are very important in the upcoming cinder release for IBM SVf Cinder Driver : 925450: [IBM SVf driver] Adding support for temporary volumegroup | https://review.opendev.org/c/openstack/cinder/+/925450 926844: [IBM SVf Driver] Added support for volumegroup-snapshot for temporary volumegroup | https://review.opendev.org/c/openstack/cinder/+/926844 916722: [IBM SVf Driver] Added support for restorefromsnapshot CLI for volumegroups | https://review.opendev.org/c/openstack/cinder/+/916722 938771: [IBM SVf Driver] Added support of clone operation for volumegroup | https://review.opendev.org/c/openstack/cinder/+/938771 929906: Doc: Documentation updates for ibm-svf-volumegroup feature. | https://review.opendev.org/c/openstack/cinder/+/929906 They are dependent on each other and our upcoming features are all dependent on these reviews. Zuul has passed on these and our internal customer reviews are also completed. Requesting you to please review them and help us merge them in the upcoming release. Thanks and Regards, Harsh

2 1

October 2025 PTG Team Signup Kickoff
by Kendall Nelson 10 Jun '25

10 Jun '25

Hello Everyone! The next OpenInfra PTG[1] will take place October 27-31, 2025 and registration for the event is now open[2]! To sign your team up, you must complete the survey[3] by September 14th at 19:00 UTC. If your team is not interested in participating, there is no need to fill out the survey. The contact information (email and preferably also IRC nickname) in the form will be used to share important details with moderators about team signup and further logistics. To ensure you receive all communications please double check and submit *ACCURATE* information! If you are not on IRC, please get on the OFTC network[4] and join #openinfra-events as much of the coordination for the event will be done in the #openinfra-events channel. You are also encouraged to familiarize yourself with the PTGBot documentation[5] as well. If you have any questions, please reach out to ptg(a)openinfra.org! Information about signing up for time slots will be sent to moderators after the team signup deadline. -Kendall (diablo_rojo) [1] PTG Site: https://openinfra.org/ptg/ [2] PTG Registration: http://ptg.openinfra.org/ [3] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2025_ptg_survey [4] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [5] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst

1 0

[all] Submit Your OpenInfra Summit Talk This Week!
by Jeremy Stanley 09 Jun '25

09 Jun '25

Are you working on something exciting with OpenStack? This is your last chance to share it with the global OpenInfra community at the OpenInfra Summit Europe in Paris[0]! The CFP[1] closes this Friday, June 13, and the Summit organizers are especially looking for talks related to OpenStack. Whether you're operating production deployments, contributing upstream, or building new tools, this is the place to share your story. Sponsoring the Summit[2]? If you'd like to be part of the schedule launch marketing happening at the end of June, this Friday is also the deadline to confirm your sponsorship. Don’t miss the chance to highlight your work and connect with the global open source community. [0] My beloved French colleagues would want me to clarify that this is actually "Paris-Saclay" (but it's still very close to Paris!) [1] Sponsorship: https://summit2025.openinfra.org/sponsor [2] CFP: https://summit2025.openinfra.org/cfp -- Jeremy Stanley

1 0

[tacker] Proposal for changing IRC timeslot
by Yasufumi Ogawa 09 Jun '25

09 Jun '25

Hi tacker team, For some members joined our team recently, it's not convenient to attend the IRC meeting since they have another regular meeting at the same time. So I'd like to propose to change the meeting time from Tuesday 8:00 UTC to Monday 8:00 UTC. Let me know if you guys are not convenient, or we'll change the time from next week (16th June). Thanks, Yasufumi

1 0

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

09 Jun '25

Hello Stackers, We're 16 weeks away from the date earmarked for the coordinated 2025.2 "Flamingo" release of OpenStack [1]. OpenStack project teams are wrapping up design specifications and gearing up to land feature changes. In the past week, the OpenInfra Foundation officially joined the Linux Foundation [2]. This is a significant move for OpenStack and other projects under the OIF. I join you in hoping that this means greater acceleration for OpenStack and broader avenues to collaborate with other open source projects under the Linux Foundation. In the same week, the OpenStack Technical Committee also passed a few important resolutions. The primary one was to adopt the "Developer Certificate of Origin" [3] for contributor sign-offs beginning July 1, 2025. What does this mean for you? This means that any new patch uploaded to the OpenStack review system (https://review.opendev.org) on or after July 1, 2025, will require a "Signed-off-by" line in the commit message. Doing so indicates that you are submitting this code in adherence to the DCO, which replaces the Contributor License Agreement that we have long required. Adding a DCO sign-off can be done by using "git commit -s" when your username and email are properly configured in your Git environment. The TC encourages PTLs, project liaisons, and all maintainers to help other contributors become familiar with this change and assist anyone who may be confused by the new requirement. If you have any questions, please join us in #openstack-dev or #openstack-tc on OFTC, or ask away on this mailing list. Alongside this significant change, the TC also clarified the actions that the Election Officials will take when there is no need for an election [4]. The next elections for Project Team Leads and a portion of the OpenStack Technical Committee will occur between Aug 27, 2025, and Sep 17, 2025. The official nomination window opens at 23:45 UTC on Aug 06, 2025. However, you're welcome to submit your nomination at any time before this date. Doing so may be helpful if you plan to be away during the nomination window. OpenDev Infrastructure Administrators have now enabled all registered users to add or edit hashtags on the code review system [5]. Some project teams have long found this useful for linking related changes—hashtags in Gerrit are more versatile than topics. I hope you'll find this helpful! === Weekly Meeting === On Jun 3, 2025, the OpenStack Technical Committee held its weekly meeting as both a video conference [6] and over IRC in OFTC's #openstack-tc channel [7]. The meeting was well attended and primarily focused on the DCO (Developer Certificate of Origin) implementation, contributor experience challenges, and other open governance proposals. A key decision was to separate translation-related concerns from the main DCO implementation. The i18n SIG has been migrating from Zanata to Weblate and will explore how the DCO can be prominently enforced via Weblate. The discussion then moved on to the findings from the maintainer and contributor surveys for the Epoxy release cycle. The survey results [8] indicated that 73% of maintainers reported difficulty getting review attention, while 68% of non-maintainer contributors faced challenges in having their reviews completed. TC members brainstormed potential reasons, and some key concerns identified include: - Inconsistent review prioritization across projects - Poor visibility into project-specific review processes - Heavy reliance on Etherpads for tracking priorities - Underutilization of review priority labels in projects that have enabled them A couple of minor action items were identified for the TC and project maintainers. Project maintainers are expected to audit their CONTRIBUTING.rst files and clearly indicate how contributors can get their changes reviewed and merged. The TC also plans to enforce more structured cross-project discussions at the October PTG. As a tangential concern, we supported the idea of hosting an ops meetup at the upcoming OpenInfra Summit in Paris-Saclay [9]. The next meeting of the OpenStack TC is today, 2025-06-09, at 17:00 UTC. This meeting will be held over IRC in the #openstack-tc channel on OFTC. Please find the agenda on the meeting's wiki page [10]. I hope you'll be able to join us. === Governance Proposals === ==== Merged ==== - Replace CLA with DCO for all contributions | https://review.opendev.org/c/openstack/governance/+/950463 - Add nova-contrib repository | https://review.opendev.org/c/openstack/governance/+/951569 - Clarify actions when no elections are required | https://review.opendev.org/c/openstack/governance/+/949431 ==== Open for review ==== - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 === Upcoming Events === - 2025-06-13: CFP Closes for the OpenInfra Summit EU: https://summit2025.openinfra.org/cfp/ - 2025-06-28: OpenInfra+Cloud Native Day, Vietnam: https://www.vietopeninfra.org/void2025 - 2025-07-19: OpenInfra Days Indonesia: https://2025.openinfra.id/ 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] OIF joins Linux Foundation: https://openinfra.org/blog/openinfra-joins-linux-foundation [3] DCO enforcement from July 1, 2025: https://governance.openstack.org/tc/resolutions/20250520-replace-the-cla-wi… [4] Election amendment: https://review.opendev.org/c/openstack/governance/+/949431 [5] Hashtags on review.opendev.org: https://lists.opendev.org/archives/list/service-announce@lists.opendev.org/… [6] TC Meeting Video Recording, 2025-06-03: https://youtu.be/y0BwG8TadVk [7] TC Meeting IRC Log 2025-06-03: https://meetings.opendev.org/meetings/tc/2025/tc.2025-06-03-17.00.html [8] Contributor and Maintainer Survey: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [9] OpenInfra Summit 2025: https://summit2025.openinfra.org/ [10] TC Meeting Agenda, 2025-06-10: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 1

Api routes
by engineer2024 09 Jun '25

09 Jun '25

In openstack, is there a feature to list all the available routes for the rest api servers, instead of checking and referring the documentation? Thanks elinux

1 0