July 2025 - openstack-discuss - lists.openstack.org

[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-magnum ui] Cannot choose an external network ID when creating a cluster template
by Nguyễn Hữu Khôi 27 Aug '25

27 Aug '25

Hello, When I create a cluster template, I cannot choose an external network ID, it disappears from horizon. My env: Ubuntu 22.04 Openstack 2024.2 Thank you. Regards Nguyen Huu Khoi

3 2

[blazar] Blazar-dashboard contains non-free files (ie: minified Javascripts)
by Thomas Goirand 22 Aug '25

22 Aug '25

Hi, I've been trying to package Blazar, all is already in Debian, but I can't get blazar-dashboard in, because upstream source contains non-free files. Namely: https://github.com/openstack/blazar-dashboard/blob/master/blazar_dashboard/… is a minifed version of a much more complex package: https://github.com/apexcharts/apexcharts.js/tree/v3.31.0 Reminder: minified Javascripts are considered by most distributions (this includes Red Hat, Ubuntu, and in my case Debian) as non-free files that cannot be shipped in the distribution without the underlying source code, and packages must build from the not minified version. Could the Blazar team work on un-vendoring apexcharts.min.js, possibly removing it completely, or replacing it with a source-full version? Cheers, Thomas Goirand (zigo)

4 6

[tc][all][monasca] Retiring the Monasca project and repositories
by Goutham Pacha Ravi 07 Aug '25

07 Aug '25

Hello Stackers, We intend to retire the Monasca project [1] and all associated repositories [2]. The retirement is being proposed with the support and consent of the current core team members and the Project Team Lead (PTL) [3]. For context, the Monasca project team was marked as being inactive during the 2024.1 (Caracal) release cycle [4]. Since then, no sustained development activity has occurred. There have been no releases tagged for any of the deliverables owned by the team either, and there are no actively maintained stable branches. So, in accordance with the procedures in the OpenStack governance documentation [5], and based on the current state of the project, we propose the following repositories ahead of the 2025.2 ("Flamingo") coordinated release: - openstack/monasca-agent - openstack/monasca-api - openstack/monasca-common - openstack/monasca-events-api - openstack/monasca-log-api - openstack/monasca-notification - openstack/monasca-persister - openstack/monasca-specs - openstack/monasca-tempest-plugin - openstack/monasca-thresh - openstack/python-monascaclient - openstack/monasca-ui - openstack/monasca-transform - openstack/monasca-ceilometer - openstack/monasca-grafana-datasource - openstack/monasca-kibana-plugin - openstack/monasca-statsd Some of the current maintainers intend to fork the project and continue development independently for their purposes. This retirement does not preclude such efforts; nor does it prevent reviving the project after the retirement. If there are any objections to retiring the project, please respond to this thread. In the event there is interest in continuing Monasca within OpenStack, we would expect the project team to meet the requirements for active status [6] — including identifying a new PTL for the upcoming release cycle and demonstrating plans for sustained maintenance. Thank you to everyone who has contributed to Monasca over the years. Thanks, On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://docs.openstack.org/monasca-api/latest/ [2] https://github.com/openstack/governance/blob/624bb5bf124452eed475c9b6e62144… [3] https://review.opendev.org/c/openstack/governance/+/953671 [4] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [5] https://docs.openstack.org/project-team-guide/repository.html#retiring-a-re… [6] https://governance.openstack.org/tc/reference/new-projects-requirements.html

3 2

[dev][designate] PSA: pkg_resources is broken with newer oslo wheels on Python 3.8
by Stephen Finucane 07 Aug '25

07 Aug '25

o/ A quick PSA for a topic has come up in a few different OpenStack forums of late. As described in a recently filed setuptools bug [1], the pkg_resources found in the most recent version of setuptools to support Python 3.8 does not correctly normalize package names passed to `pkg_resources.require`. This has become an issue of late because since earlier this year the OpenStack release tooling has started (correctly) normalizing filenames of the '.whl' files uploaded to PyPI (so e.g. 'oslo.messaging' now becomes 'oslo_messaging'). You are likely to see this manifest with weird errors like `The 'package.foo>=1.2.3' distribution was not found`, when you know that it is. I have seen it pop up because either (a) pkg_resources is being invoked via an explicit call, as in some of the release tooling used in `openstack/releases`, or (b) pkg_resources is being invoked via the auto-generated import headers added by setuptools when you use its legacy "scripts" keyword rather than newer "console scripts" replacement. The latter in particular is biting some projects indirectly due to Designate and Octavia incorrectly using this mechanism to work around the demise of wsgi_scripts, and I have fixes up waiting for review [2][3]. Just sharing in case some people have seen this, because it's quite a weird corner case to hit. Stephen [1] https://github.com/pypa/setuptools/issues/5051 [2] https://review.opendev.org/c/openstack/designate/+/950569/ [3] https://review.opendev.org/c/openstack/designate/+/955683/

3 3

[all][ops][qa] Decommissioning RefStack and retiring related software
by Jeremy Stanley 05 Aug '25

05 Aug '25

The RefStack service at refstack.openstack.org has been unused for purposes of qualifying OpenStack trademark licenses[*] since March of last year, after a 2023 board resolution[**] relaxed the former requirement for it. Effective immediately, the service is being decommissioned along with any associated resources, and the related Git repositories in OpenDev (interop, refstack, refstack-client) will be officially retired in the near future as well. Let me know if you have any questions or concerns. [*] https://openinfra.org/legal/trademark-policy [**] https://board.openinfra.org/meetings/minutes/05122023BoardMinutes -- Jeremy Stanley on behalf of the OpenInfra Foundation

4 3

[kolla][barbican] Secure password management in Kolla-Ansible using Castellan
by elnazcloud＠gmail.com 05 Aug '25

05 Aug '25

Hi all, I have deployed an OpenStack environment using Kolla Ansible. I'm looking for a way to avoid storing service passwords (e.g., database, keystone, etc.) in clear text inside the configuration files. Is there any recommended method to integrate Barbican and Castellan so that services like Nova, Keystone, or Cinder can fetch secrets securely during runtime using oslo.config? If not natively supported, are there best practices or known workarounds for achieving this securely in a Kolla-based deployment? Thanks in advance!

7 12

[Zed][Neutron][OVN] Severe VM Network Performance Degradation Compared to Host
by Jeff Yang 05 Aug '25

05 Aug '25

Hi all, I'm running OpenStack Zed with OVN as the Neutron backend. I've encountered a severe VM network performance degradation issue and would appreciate any insights from the community. 🔹 **Environment** - OpenStack version: Zed - Neutron backend: OVN - Two VMs (each 4 vCPUs, 8 GB RAM) launched on two different compute nodes - Multi-queue is enabled on the VM vNICs 🔹 **Issue** The network performance inside the VMs is significantly worse than on the host nodes, with high packet retransmissions observed. 🔹 **Test results** **Host-to-Host (VTEP IPs)** ``` $ iperf3 -c 192.168.152.152 Connecting to host 192.168.152.152, port 5201 [ 5] local 192.168.152.153 port 45352 connected to 192.168.152.152 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 1.38 GBytes 11.8 Gbits/sec 0 3.10 MBytes [ 5] 1.00-2.00 sec 1.37 GBytes 11.8 Gbits/sec 0 3.10 MBytes [ 5] 2.00-3.00 sec 1.42 GBytes 12.2 Gbits/sec 0 3.10 MBytes [ 5] 3.00-4.00 sec 1.39 GBytes 11.9 Gbits/sec 0 3.10 MBytes [ 5] 4.00-5.00 sec 1.38 GBytes 11.8 Gbits/sec 0 3.10 MBytes [ 5] 5.00-6.00 sec 1.43 GBytes 12.3 Gbits/sec 0 3.10 MBytes [ 5] 6.00-7.00 sec 1.41 GBytes 12.1 Gbits/sec 0 3.10 MBytes [ 5] 7.00-8.00 sec 1.41 GBytes 12.1 Gbits/sec 0 3.10 MBytes [ 5] 8.00-9.00 sec 1.41 GBytes 12.1 Gbits/sec 0 3.10 MBytes [ 5] 9.00-10.00 sec 1.42 GBytes 12.2 Gbits/sec 0 3.10 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 14.0 GBytes 12.0 Gbits/sec 0 sender [ 5] 0.00-10.04 sec 14.0 GBytes 12.0 Gbits/sec receiver iperf Done. ``` **VM-to-VM (through overlay network)** ``` $ iperf3 -c 10.0.6.10 Connecting to host 10.0.6.10, port 5201 [ 5] local 10.0.6.37 port 56710 connected to 10.0.6.10 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 499 MBytes 4.19 Gbits/sec 263 463 KBytes [ 5] 1.00-2.00 sec 483 MBytes 4.05 Gbits/sec 467 367 KBytes [ 5] 2.00-3.00 sec 482 MBytes 4.05 Gbits/sec 491 386 KBytes [ 5] 3.00-4.00 sec 483 MBytes 4.05 Gbits/sec 661 381 KBytes [ 5] 4.00-5.00 sec 472 MBytes 3.95 Gbits/sec 430 391 KBytes [ 5] 5.00-6.00 sec 480 MBytes 4.03 Gbits/sec 474 350 KBytes [ 5] 6.00-7.00 sec 510 MBytes 4.28 Gbits/sec 567 474 KBytes [ 5] 7.00-8.00 sec 521 MBytes 4.37 Gbits/sec 565 387 KBytes [ 5] 8.00-9.00 sec 509 MBytes 4.27 Gbits/sec 632 483 KBytes [ 5] 9.00-10.00 sec 514 MBytes 4.30 Gbits/sec 555 495 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 4.84 GBytes 4.15 Gbits/sec 5105 sender [ 5] 0.00-10.05 sec 4.84 GBytes 4.14 Gbits/sec receiver iperf Done. ``` As you can see, there's a sharp drop in performance inside the VMs (from ~12 Gbps down to ~4 Gbps), with a lot of retransmissions in 10 seconds. Has anyone encountered a similar issue with OVN and VM networking performance? What could be the potential causes? Any suggestions or debugging tips are welcome. Thanks in advance! Best regards,

5 4

[Neutron] - General thoughts on tenancy network MTU
by Karl Kloppenborg 01 Aug '25

01 Aug '25

Hi Neutrinos, I was discussing with a colleague about our MTU settings within our Openstack regions, generally speaking we have a physnet_global_mtu of 1550 with tenancy networks automatically provisioned as 1500 VXLAN. This ends up with VM’s receiving DHCP MTU settings of 1500 which is fine, however reading about yesterday’s discussion on OVN performance, Nguyen’s recommendation was to enable Jumboframes. This got me thinking, what do you set your tenancy and phynet MTU’s to? Very interested to hear about your experiences with running 9k MTU’s on the VM networks etc, what impact this has on OVS/OVN routers and northbound connectivity being 1500. 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>

2 1

(Ceilometer) Openstack - Kolla-Ansible deployment - Ceilometer (Central & compute) Docker Containers are unhealthy
by TRB PREM KUMAR 01 Aug '25

01 Aug '25

Hi, We have deployed an all-in-one OpenStack server for billing. Now ceilometer containers are unhealthy. Please help us to resolve this issue. Reference Output for reference: trb1@openstack-aio-01:~$ docker ps | grep ceil c53fc69ba42b quay.io/openstack.kolla/ceilometer-compute:2024.2-rocky-9 "dumb-init --single-…" About a minute ago Up About a minute *(unhealthy) * ceilometer_compute 9337af646e0f quay.io/openstack.kolla/ceilometer-central:2024.2-rocky-9 "dumb-init --single-…" 30 minutes ago Up About a minute ( *unhealthy)* ceilometer_central 554c4b8ccd86 quay.io/openstack.kolla/ceilometer-notification:2024.2-rocky-9 "dumb-init --single-…" 4 days ago Up About a minute (healthy) ceilometer_notification *** Logs files are attached for reference. Regards, TRB.

3 6

[scientific-sig][help] Research about private cloud
by Winicius Allan 31 Jul '25

31 Jul '25

Hi all! I'm about to write my final paper, and I want to research something related to OpenStack and private clouds. If someone wants to take the time to discuss the problems in your environment, I'd be very glad!What I had on my mind is: - There is something that could improve utilization and performance when the user is not charged about their use on a private cloud. - There is any process scheduling algorithm that could be used on specific workloads instead of Linux default scheduler that can improve application performance? I was thinking about using eBPF here. Best regards.

2 1

[cinder] AttributeError: 'Volume' object has no attribute 'use_quota'
by Kees Meijs | Nefos 31 Jul '25

31 Jul '25

Hello Stackers, It seems we're hitting a bug within the Cinder Volume service. The problem presents itself when creating a Ceph RBD backed Volume using an originating snapshot. > 2025-07-31 19:02:54.896 3602390 WARNING cinder.volume.manager > [req-a476ac04-ee6c-4335-8fca-e606616a5959 > eccdb27249254d9d9fb73570f5de8877 d678ba8e1dee4f7484555580d0a61562 - - > -] Task > 'cinder.volume.flows.manager.create_volume.CreateVolumeFromSpecTask;volume:create' > (03c06b47-7df3-4427-8ad0-61f9a97d0159) transitioned into state > 'FAILURE' from state 'RUNNING' > 5 predecessors (most recent first): > </snip (maybe the Atoms are needed and if so I could redact those)> > |__Flow 'volume_create_manager': AttributeError: 'Volume' > object has no attribute 'use_quota' > 2025-07-31 19:02:54.896 3602390 ERROR cinder.volume.manager Traceback > (most recent call last): > 2025-07-31 19:02:54.896 3602390 ERROR cinder.volume.manager File > "/usr/lib/python3/dist-packages/taskflow/engines/action_engine/executor.py", > line 53, in _execute_task > 2025-07-31 19:02:54.896 3602390 ERROR cinder.volume.manager result = > task.execute(**arguments) > 2025-07-31 19:02:54.896 3602390 ERROR cinder.volume.manager File > "/usr/lib/python3/dist-packages/cinder/volume/flows/manager/create_volume.py", > line 1158, in execute > 2025-07-31 19:02:54.896 3602390 ERROR cinder.volume.manager > model_update = self._create_from_snapshot(context, volume, > 2025-07-31 19:02:54.896 3602390 ERROR cinder.volume.manager File > "/usr/lib/python3/dist-packages/cinder/volume/flows/manager/create_volume.py", > line 461, in _create_from_snapshot > 2025-07-31 19:02:54.896 3602390 ERROR cinder.volume.manager > model_update = self.driver.create_volume_from_snapshot(volume, > 2025-07-31 19:02:54.896 3602390 ERROR cinder.volume.manager File > "/usr/lib/python3/dist-packages/cinder/volume/drivers/rbd.py", line > 1069, in create_volume_from_snapshot > 2025-07-31 19:02:54.896 3602390 ERROR cinder.volume.manager if > int(volume.size): > 2025-07-31 19:02:54.896 3602390 ERROR cinder.volume.manager > AttributeError: 'Volume' object has no attribute 'use_quota' > 2025-07-31 19:02:54.896 3602390 ERROR cinder.volume.manager Yes, this reflects a non-current version, to be precise Cinder 17.4. However, does this look familiar to someone, maybe? Thanks! Cheers, Kees

1 1

[Neutron] ML2: Can Operators Safely Extend binding:profile with Custom Keys?
by cxue22＠bloomberg.net 31 Jul '25

31 Jul '25

Hi all, I'm working on a Neutron customization to expose and manage data in the `binding:profile` field stored in the `ml2_port_bindings` table, and I have a few questions around operator and third-party plugin compatibility — particularly in reference to the blueprint: https://blueprints.launchpad.net/neutron/+spec/ml2-binding-profile As I understand it, the `binding:profile` is represented as a string column containing a JSON dictionary that can be passed by the compute agent and interpreted by ML2 mechanism drivers during port binding. My intent is to: - Create a custom API endpoint that allows reading and updating specific key/value pairs in this JSON dictionary. - Enable third-party mechanism drivers and operators to add custom fields to this profile. My main question is: **Are operators and third-party ML2 drivers free to add arbitrary key/value pairs to the `binding:profile` dictionary, and can those be expected to persist across Neutron upgrades and database migrations?** Additionally: - Are there any best practices or expectations around namespacing or schema validation of custom fields in `binding:profile`? - Are there known caveats or upgrade scenarios where such data may be truncated, filtered, or overwritten? I'd appreciate any guidance from the Neutron community on how this field is intended to be extended or preserved, and whether such customization is supported in the long term. Thanks in advance! Best regards, Chang Xue Bloomberg Engineering

3 3

[openstack][magnum]Cannot upgrade clusters
by Nguyễn Hữu Khôi 31 Jul '25

31 Jul '25

Hello. I cannot upgrade clusters via magnum_cluster_api. These are log from magnum_api: https://anotepad.com/notes/c9h8bd55 OPS: 2025.1 OS: Ubuntu 24.04 magnum_cluster_api: v0.30.0 Would you give some ideas on it? Thank you! Nguyen Huu Khoi

1 1

[Neutron][VPNaaS] Multiple tunnels per IPSec Service
by Shubham Yadav 31 Jul '25

31 Jul '25

Hello OpenStack Community, I'm working with OpenStack VPNaaS (using strongSwan as the backend driver) and have a question about tunnel configuration capabilities. *Current Setup:* OpenStack VPNaaS with strongSwan driver (StrongSwanDriver) Single VPN Service (gateway) with multiple IPSec Site Connections Each connection targets different remote peers with distinct subnets *Configuration Details:* VPN Service: Connected to a single router Multiple IPSec Site Connections under the same VPN Service: Connection 1: To MY office (10.10.100.0/24) via peer 68.x.y.34 Connection 2: To Rackspace (172.24.60.0/22) via peer 184.n.p.53 Shared IKE and IPSec policies across connections Local endpoint groups covering multiple subnets (192.168.0.0/24, 10.43.0.0/16) *Question:*Is it supported/recommended to have multiple IPSec Site Connections under a single VPN Service? I understand this creates multiple tunnels from the same OpenStack router to different remote peers. *Current Issue:*One of my connections shows "PENDING_CREATE" status while the other is "ACTIVE". I'm trying to determine if this is: A configuration issue on my end A limitation of having multiple tunnels per VPN service A strongSwan-specific behavior in the OpenStack context *Specific Questions:* Does VPNaaS officially support multiple IPSec connections per VPN Service? Are there any known limitations or best practices when using multiple tunnels? Should each remote site have its own dedicated VPN Service instead? I've checked the documentation but couldn't find clear guidance on multi-tunnel scenarios. Any insights from the community would be greatly appreciated. *Environment:* OpenStack version: 2024.2 Dalmatian Neutron VPNaaS with strongSwan backend Kubernetes-deployed OpenStack (OpenStack-Helm) Thank you for your time and assistance! Best regards, Shubham

1 0

[Neutron][VPNaaS] Multiple tunnels per IPSec Service
by Shubham Yadav 31 Jul '25

31 Jul '25

Hello OpenStack Community, I'm working with OpenStack VPNaaS (using strongSwan as the backend driver) and have a question about tunnel configuration capabilities. Current Setup: OpenStack VPNaaS with strongSwan driver (StrongSwanDriver) Single VPN Service (gateway) with multiple IPSec Site Connections Each connection targets different remote peers with distinct subnets Configuration Details: VPN Service: Connected to a single router Multiple IPSec Site Connections under the same VPN Service: Connection 1: To MY office (10.10.100.0/24) via peer 68.x.y.34 Connection 2: To Rackspace (172.24.60.0/22) via peer 184.n.p.53 Shared IKE and IPSec policies across connections Local endpoint groups covering multiple subnets (192.168.0.0/24, 10.43.0.0/16) Question: Is it supported/recommended to have multiple IPSec Site Connections under a single VPN Service? I understand this creates multiple tunnels from the same OpenStack router to different remote peers. Current Issue: One of my connections shows "PENDING_CREATE" status while the other is "ACTIVE". I'm trying to determine if this is: A configuration issue on my end A limitation of having multiple tunnels per VPN service A strongSwan-specific behavior in the OpenStack context Specific Questions: Does VPNaaS officially support multiple IPSec connections per VPN Service? Are there any known limitations or best practices when using multiple tunnels? Should each remote site have its own dedicated VPN Service instead? I've checked the documentation but couldn't find clear guidance on multi-tunnel scenarios. Any insights from the community would be greatly appreciated. Environment: OpenStack version: 2024.2 Dalmatian Neutron VPNaaS with strongSwan backend Kubernetes-deployed OpenStack (OpenStack-Helm) Thank you for your time and assistance! Best regards, Shubham

1 0

[Ovs-dpdk]Issue with ovs-dpdk deployment in Kolla-Ansible (zed)
by samira_darvishnia＠yahoo.com 31 Jul '25

31 Jul '25

Hi all, I'm trying to deploy OVS-DPDK using Kolla-Ansible Zed, and I'm running into a blocking issue during deployment. I would really appreciate your insights or suggestions. Problem Summary: During the deployment of ovs-dpdk, the container ovsdpdk-vswitchd fails to start, with the following error in its logs: + echo 'Running command: '\''/usr/sbin/ovs-vswitchd unix:/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info --mlockall --log-file=/var/log/kolla/openvswitch/ovs-vswitchd.log --pidfile'\''' + exec /usr/sbin/ovs-vswitchd unix:/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info --mlockall --log-file=/var/log/kolla/openvswitch/ovs-vswitchd.log --pidfile Running command: '/usr/sbin/ovs-vswitchd unix:/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info --mlockall --log-file=/var/log/kolla/openvswitch/ovs-vswitchd.log --pidfile' ovs-vswitchd: invalid option -- 'w' ovs-vswitchd: invalid option -- 'w' EAL: FATAL: Invalid 'command line' arguments. 2025-07-30T13:44:59Z|00017|dpdk|EMER|Unable to initialize DPDK: Invalid argument ovs-vswitchd: Cannot init EAL (Invalid argument) This appears to be related to an incorrect parsing of arguments for ovs-vswitchd. What I’ve tried: I already applied this patch (as referenced in Gerrit): https://review.opendev.org/c/openstack/kolla-ansible/+/913653/1/ansible/rol… However, the issue still persists. Additional context: • Deployment hangs on the task: name: Wait for dpdk tunnel ip It waits for 5 minutes and then fails. • The parameter dpdk_tunnel_interface_address is already set in my global.yml. • I’ve configured and bound NICs to vfio-pci. • Environment info: • OpenStack Zed • Kolla-Ansible Zed • dpdk_tunnel_interface_address is set • OVS-DPDK is containerized via Kolla Has anyone seen this issue before or can suggest further steps? Any insight on how to correctly pass EAL arguments or what else might be misconfigured would be very helpful. Thanks in advance, Samira

1 0

[Neutron][Tacker][Issue Investigation] Issue with Neutron in Tacker Zuul Patches �C Suspected Regression in Neutron Master Branch
by Renu Rani 30 Jul '25

30 Jul '25

Hi Neutron Team, We are currently facing an issue in Tacker Zuul patch jobs build (with master branch), where the DevStack setup fails during the initial Neutron network creation step. Problem statement: The failure occurs at this point in the stack.sh script, for devstack environment creation in build process. Below command execution is failing in stack.sh [openstack --os-cloud devstack-admin-demo --os-region RegionOne router add subnet 20b264df-5f19-4599-a83d-2e76e7cbf5dc d777d04b-93ff-4e94-b6a9-cc8de3e23921] Error Message: This results in a 500 Internal Server Error, as seen in the logs: [HttpException: 500: Server Error for url: http://10.x.x.x/networking/v2.0/routers/20b264df-5f19-4599-a83d-2e76e7cbf5d…] Analysis for the issue: Below error is coming in Neutron API logs: [ERROR neutron.plugins.ml2.ovo_rpc RuntimeError: cannot notify on un-acquired lock] 1. Tried overriding the required-projects in Zuul to use stable/2025.1 branches (instead of master) to identify project(master branch) which is causing root cause. 2. Tacker team has created DNM patch (952892) to invetsigate this in detail. https://review.opendev.org/c/openstack/tacker/+/952892 1. In DNM patch Patchset 11 (on June 29), we have taken devstack stable/2025.1. In stable branch the devstack environment created sucessfully. 2. In DNM patch Patchset 25 (on July 8), with the same devstack override (stable/2025.1), the job now fails earlier during DevStack setup. The logs show that Neutron failed to start, causing the job to fail across all nodes. As per observations and anlysis seems the recent changes in the Neutron master branch between June 29 and July 8 might be causing this issue. We’d appreciate your help in reviewing the changes in Neutron's master branch during that window that could cause this behavior and suggesting any debugging approaches or patches we can test on tacker. Please let us know if you'd like additional logs or info from the Zuul job runs. Thanks in advance for your support! Thanks & Regards, Renu Rani (レヌラニ) Mobile: +91-9311888962 E-mail: renu.rani(a)india.nec.com<mailto:renu.rani@india.nec.com> The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NEC Corporation India Private Limited or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NEC Corporation India Private Limited or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.

5 10

[neutron] Is NVIDIA ASAP2 offloading with OpenStack just a myph?
by Vasyl Saienko 30 Jul '25

30 Jul '25

Hello OpenStack community, I'm trying to set up OpenStack with Nvidia ASAP2 hardware offloading in switchdev mode according to OpenStack guidelines <https://docs.openstack.org/neutron/latest/admin/config-ovs-offload.html> and Nvidia guidelines <https://docs.nvidia.com/doca/sdk/ovs-kernel+hardware+offloads/index.html> on the ConnectX6DX. I've tried different network types VLAN and VXLAN but offloading for none of them works. From an OpenStack standpoint everything is configured according to documentation, representor device is created and plugged in the br-int bridge (eth14) physical. PF enp33s0f0np0 is set to switchdev mode ``` devlink dev eswitch show pci/0000:21:00.0 pci/0000:21:00.0: mode switchdev inline-mode none encap-mode basic ``` ``` root@kaas-node-52648a8f-cbfd-4b9a-b392-1594b1d97cfa:~# ovs-vsctl show 12e00cdb-6520-4666-908f-57f59e8b9bd4 Manager "ptcp:6640:127.0.0.1" is_connected: true Bridge br-ex Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port br-ex Interface br-ex type: internal Port pr-floating Interface pr-floating Port phy-br-ex Interface phy-br-ex type: patch options: {peer=int-br-ex} Bridge br-int Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port br-int Interface br-int type: internal Port int-br-tenant Interface int-br-tenant type: patch options: {peer=phy-br-tenant} Port tap58ac2b17-fb tag: 1 Interface tap58ac2b17-fb Port int-br-ex Interface int-br-ex type: patch options: {peer=phy-br-ex} Port eth14 tag: 1 Interface eth14 Bridge br-tenant Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port br-tenant Interface br-tenant type: internal Port phy-br-tenant Interface phy-br-tenant type: patch options: {peer=int-br-tenant} Port enp33s0f0np0 Interface enp33s0f0np0 Bridge br-tun Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} ovs_version: "3.0.0-0056-25.04-based-3.3.5" ``` But hardware offloading is not happening, tcpdump on eth14 still shows all packets, and no TC rules are created. OpenStack uses complex openvswitch rules to setup virtual networking, in this scenario vlan tagging is done by the following rule ``` cookie=0x45b91976d5c4f175, duration=233.443s, table=60, n_packets=314, n_bytes=35574, priority=100,in_port=eth14 actions=set_field:0x11->reg5,set_field:0x1->reg6,resubmit(,73) ``` If we simplify openflow rules and align them with Nvidia guidelines for openvswitch hardware offloading by plugging representor device directly into physnet bridge, and assign vlan tag as port attribute hardware offloading starts working. ``` root@kaas-node-52648a8f-cbfd-4b9a-b392-1594b1d97cfa:~# ovs-vsctl del-port eth14 root@kaas-node-52648a8f-cbfd-4b9a-b392-1594b1d97cfa:~# ovs-vsctl add-port br-tenant eth14 root@kaas-node-52648a8f-cbfd-4b9a-b392-1594b1d97cfa:~# ovs-vsctl set port eth14 tag=1443 ``` ``` root@kaas-node-52648a8f-cbfd-4b9a-b392-1594b1d97cfa:~# for i in $(ip link | awk '{print $2}' |grep -e enp -e ens |grep -v vf$); do tc filter show dev $i ingress; done filter protocol 802.1Q pref 6 flower chain 0 filter protocol 802.1Q pref 6 flower chain 0 handle 0x1 vlan_id 1443 vlan_prio 0 vlan_ethtype arp dst_mac fa:16:3e:36:1b:90 src_mac fa:16:3e:39:90:d8 eth_type arp in_hw in_hw_count 1 action order 1: vlan pop pipe index 1 ref 1 bind 1 no_percpu used_hw_stats delayed action order 2: mirred (Egress Redirect to device eth14) stolen index 1 ref 1 bind 1 cookie 4b5b5a701f4e3fee7ac1c198037522e3 no_percpu used_hw_stats delayed ``` Similar issue occurs when using the VXLAN network. OpenStack setup VXLAN tunnel like, where tunnel_id is inserted dynamically via openflow rules (in_key=flow) ``` Port vxlan-0a0c0004 Interface vxlan-0a0c0004 type: vxlan options: {df_default="true", dst_port="4790", egress_pkt_mark="0", in_key=flow, local_ip="10.12.0.9", out_key=flow, remote_ip="10.12.0.4"} ``` In this configuration hardware offloading is not happening neither. But when setting up vxlan according to nvidia guidelines (no complex rules are involved) hardware offloading starts working (tcpdump for representor device shows only first packet and tc rules are being created). ``` Port vxlan3 Interface vxlan3 type: vxlan options: {key="60987", local_ip="10.12.0.9", remote_ip="10.12.0.4"} ``` ``` Cannot find device "enp33s0f0npf0vf" Cannot find device "veth68d427d@if1" filter protocol ip pref 2 flower chain 0 filter protocol ip pref 2 flower chain 0 handle 0x1 dst_mac fa:16:3e:65:0c:6d src_mac 52:5a:d0:9e:8a:32 eth_type ipv4 enc_dst_ip 10.12.0.9 enc_src_ip 10.12.0.8 enc_key_id 60987 enc_dst_port 4789 enc_tos 0 ip_flags nofrag in_hw in_hw_count 2 action order 1: tunnel_key unset pipe index 2 ref 1 bind 1 no_percpu used_hw_stats delayed action order 2: mirred (Egress Redirect to device eth15) stolen index 2 ref 1 bind 1 cookie 5d44cdf6754fc237cc0bd688a6fe70a8 no_percpu used_hw_stats delayed ``` Am I doing something wrong? Is there anyone who has other results? -- <https://www.mirantis.com/> Vasyl Saienko Principal DevOps Engineer vsaienko(a)mirantis.com <dstoltenberg(a)mirantis.com> +(380) 66 072 07 17 <++1+(650)+564+7038>

3 3

Openstack integration with openid as leycloak
by amine belroul 30 Jul '25

30 Jul '25

Hello, Is there any detailed docs can help me to integrate openstack with openid? Please multi domains and multi projects.

3 2

[Cinder] pbm configuring multipath on NVMeoF
by Vincent Godin 30 Jul '25

30 Jul '25

Hello guys, Openstack: 2025.1 OS: Ubuntu 24.04 We are having trouble configuring multipath on a NetApp backend using NVMe over TCP. After reading numerous articles on this issue, we concluded that it was necessary to operate in native multipath mode, which is enabled by default on Ubuntu 24.04, and that it is no longer necessary to keep the multipathd service active for this to work. We ran inconclusive tests by setting the "use_multipath_for_image_xfer" and "enforce_multipath_for_image_xfer" variables to true in cinder.conf. We also set the "volume_use_multipath variable" to true in the libvirt section of nova.conf, but without success. After creating an instance and a volume on a server with Openstack, when querying the subsystem with the nvme command, we only get a single path. But when we query the backend from the same server with "nvme discover," we do get four paths. In the os-brick code, we see that it checks a Multipath variable that must be set to true... I think this is purely a configuration issue, but the examples given by various manufacturers (NetApp, PureStorage, etc.) don't indicate anything in particular. So, does anyone know the configuration to apply for multipath to work (cinder/nova)? Thank you.

3 8

OpenStack for AI Whitepaper
by Kendall Nelson 29 Jul '25

29 Jul '25

Hello Folks! As you might have heard, the OpenInfra AI WG has been starting to put together an OpenStack for AI Whitepaper and we wanted to formally invite you all to attend the WG's meetings and working sessions, to get involved on working group's the mailing list <https://lists.openinfra.org/mailman3/lists/ai-openstack-wg.lists.openinfra.…> and to help us shape the whitepaper into a resource for those looking to understand just how OpenStack is capable of serving AI workloads. We could really benefit from your innate understanding of how the OpenStack services work and also hope to surface feedback and questions from the group for the larger OpenStack community in future meetings. Also, we have organizations volunteering to do show and tell sessions about their OpenStack clouds hosting AI workloads and discussing pain points, lessons learned etc. The next of those show and tell sessions will take place on September 29. We have a meeting coming this week on Thursday at 13 UTC in this google meet <http://meet.google.com/wzn-jgcn-cfj>. If you would like an actual calendar invite, please reach out and I will make sure you are added! -- Kendall Nelson *Senior Upstream Developer Advocate* The OpenInfra Foundation <https://openinfra.dev/>

1 1

[kolla] IRC meeting cancelled - 30-th of July 2025
by Bartosz Bezak 29 Jul '25

29 Jul '25

Hello, Due to limited availability of the Kolla core team members, tomorrow’s Kolla IRC meeting is cancelled. Best regards, Bartosz Bezak

1 0

[publiccloud-sig] Public Cloud SIG meeting d.d. 30 July
by Kees Meijs | Nefos 29 Jul '25

29 Jul '25

Hello Stackers, Tomorrow (that's 30 July) 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.

1 0

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

28 Jul '25

Hello Stackers, We're a month away from the feature freeze date for the 2025.2 ("Flamingo") release cycle [1], scheduled for 2025-08-28. OpenStack project teams are observing various internal deadlines prior to that important date to ensure a complete and timely release. As we look ahead, OpenStack's election officials will begin accepting self-nominations for the upcoming Project Team Lead roles and four seats on the OpenStack Technical Committee starting 2025-08-06 [2]. The nomination deadline is two weeks later, on 2025-08-20. You are welcome to submit an early nomination [3] now if you anticipate being away during the nomination window. To be a Project Team Lead candidate, you must be an Active Project Contributor—i.e., someone who has contributed to the project you wish to lead in the past 12 months (counted up to 2025-08-20). Any individual member of the OpenInfra Foundation, regardless of contributor status, may propose their candidacy for the OpenStack Technical Committee. To vote in these elections, you must be a member of the OpenInfra Foundation [4] and an active contributor—either through merged contributions to official projects or via nomination by a project’s PTL, liaisons, any Special Interest Group, or the OpenStack Technical Committee [5]. To receive your ballot, please ensure your email address is added in Gerrit and that you've opted in to receive emails from CIVS before 2025-08-20: https://civs1.civs.us/cgi-bin/opt_in.pl In the past week, the TC approved revised milestones for the cross-project goal of removing the use of Eventlet [6]. We still aim to drop Eventlet usage completely in the 2027.2 ("J") release. The "aetos" project now has a canonical service type called "metric-storage" [7]. Several other governance changes are currently under community review. === Weekly Meeting === The last weekly meeting of the OpenStack TC took place [8] on 2025-07-22, with a smaller attendance than usual. We expect this trend to continue through the summer break in the northern hemisphere. Key updates included changes to the Eventlet-removal goal timeline and a deeper look into the prolonged inactivity of the Monasca project team. While volunteers have consistently expressed interest in maintaining the project, it hasn’t met reactivation milestones since its last active cycle (2024.1). However, some improvements have been merged across the team’s repositories. The TC agreed to enforce a more formal and transparent process: projects must explicitly request extensions to inactive status [9], and future documentation will include retirement deadlines that compel TC votes on any extensions. We'll continue discussing the next steps for Monasca through governance proposals and this mailing list. Opendev administrators informed us that they completed the transition off Nodepool, and Debian Trixie images are nearly ready for testing. This is also useful for transitioning the Ceph CI job to Debian to enable faster fixes in the client software. In open discussion, the group revisited the definition of corporate affiliation in the TC charter. A proposal will be made to clarify what affiliation diversity means and how/why it should be disclosed during elections. The next meeting of the OpenStack Technical Committee is today, 2025-07-29. It will be hosted on the #openstack-tc channel on OFTC at 1700 UTC. Please find the meeting's agenda and other details on its wiki page [10]. I hope you'll be able to join us. === Governance Proposals === === Merged === - Make Eventlet removal deadlines more acceptable for operators | https://review.opendev.org/c/openstack/governance/+/952903 - Retire networking-midonet | https://review.opendev.org/c/openstack/governance/+/955364 === Open for review === - Define "affiliation" within the context of the TC | https://review.opendev.org/c/openstack/governance/+/956024 - Add series names to runtimes doc | https://review.opendev.org/c/openstack/governance/+/955810 - Remove Monasca from active project | https://review.opendev.org/c/openstack/governance/+/953671 - os-test-images never releases | https://review.opendev.org/c/openstack/governance/+/954249 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 === Upcoming Events === - 2025-08-06: Nominations open for OpenStack elections: https://governance.openstack.org/election/ - 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/ 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://governance.openstack.org/election/ [3] Submitting your candidacy: https://governance.openstack.org/election/#how-to-submit-a-candidacy [4] Join the OpenInfra Foundation: https://openinfra.org/join/individual/ [5] Who is an Active Contributor: https://governance.openstack.org/tc/reference/charter.html#voters-for-tc-se… [6] Eventlet removal timeline: https://governance.openstack.org/tc/goals/selected/remove-eventlet.html#com… [7] OpenStack service types: https://specs.openstack.org/openstack/service-types-authority/#service-data [8] TC Meeting IRC Log 2025-07-22: https://meetings.opendev.org/meetings/tc/2025/tc.2025-07-22-17.00.html [9] Emerging and inactive projects: https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [10] TC Meeting Agenda, 2025-07-29: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[manila] Flamingo Mid Cycle: Aug 6 - 7th
by Carlos Silva 28 Jul '25

28 Jul '25

Hello, Zorillas and interested stackers, The OpenStack Manila's mid cycle event [1] will take place on Aug 6th and 7th, from 14 to 16 UTC. More details on the .ics file [1]. At the event, we will focus on checking on the progress of the deliverables we planned for this cycle, as well as do collaborative review sessions for the features being proposed to speed up the review process. If you have a topic you would like to discuss, please add them to the mid cycle etherpad [2]. [1] https://gist.github.com/silvacarloss/598ad6d311cfe0a588b6b47ea979dff5 [2] https://etherpad.opendev.org/p/manila-flamingo-mid-cycle Looking forward to it, carloss

1 0

[i18n] Sharing CMU Students’ Contributions: Progress on Zanata-to-Weblate Migration
by Ian Y. Choi 28 Jul '25

28 Jul '25

Dear OpenStack Community, Over the past six weeks, Seongsoo and I had the privilege of mentoring a group of four students from Carnegie Mellon University (CMU) [1] as part of our ongoing effort to migrate the OpenStack Internationalization (I18n) platform from Zanata to Weblate. I would like to take this opportunity to highlight the significant and meaningful contributions made by three students, Furqan Saeed, Simon Yu, and Jana Hussien, who recently completed video demos showcasing their work [2] [3]. Project Context As many may know, the I18n SIG has been working to modernize our translation infrastructure by transitioning from Zanata (now unmaintained) to Weblate — an actively developed, open source platform. This project not only ensures the sustainability of our translations, but also offers a valuable learning path for new contributors. Below are the key outcomes achieved by Furqan, Simon and Jana: 1. i18n tools script test codes for Weblate (by Furqan Saeed & Simon Yu) Furqan and Simon focused on bringing robust, production-quality unit testing to the collection of Python scripts and tools responsible for Weblate integration. Furqan’s video [2] demonstrates these efforts. Together, they: Developed a comprehensive suite of ~34 unit tests covering the main Weblate tool files. Used Python’s unittest and mocking strategies to ensure functions behave as expected, even simulating server responses. Noted and addressed gaps in requirements, such as missing library dependencies. Provided clear documentation (README.rst) explaining test infrastructure and file structure. Gained and demonstrated familiarity with OpenStack’s development guidelines, Gerrit workflows, and CI requirements. Their efforts establish a much needed test baseline for future improvements and bring our I18n tooling closer to OpenStack’s best practices. This contribution not only enhances software reliability but also creates a safer, more efficient environment for future contributors. 2. Migration of Zuul infrastructure scripts to Weblate (by Jana Hussien) Jana concentrated on migrating and refactoring the automation scripts that enable daily translation updates in Zuul, shifting from Zanata to Weblate. Her work involved: Analyzing and translating the logic in current scripts to ensure seamless migration, including first-time migration routines for new projects. Developing new scripts to automate creation of Weblate components and upload of translation templates (POT) and PO files; handling language code transformations between platforms. Troubleshooting integration challenges between Weblate’s API/CLI and OpenStack workflows, identifying and overcoming tricky configuration issues related to version control structure. Successfully demonstrating the migration workflow for projects such as trove-dashboard and horizon, with detailed documentation of results. Improving operational resilience by implementing enhanced error handling and summary reporting in the scripts. Discovering and addressing several issues during live testing, and documenting workarounds and plans for future improvements. Jana has also outlined next steps, including integrating these scripts further into the Zuul pipeline, modularizing code, and enhancing public documentation. These contributions represent valuable progress toward a full, sustainable migration to Weblate - benefiting the entire OpenStack community by advancing our translation workflows and broadening global accessibility. On behalf of all mentors (myself, Seongsoo Cho, Goutham Pacha Ravi), I’d like to thank Furqan, Simon, and Jana for their hard work, dedication, and collaborative spirit, and encourage other students and new contributors to get involved. If anyone would like to review their code, documentation, or get involved in this effort, please feel free to reach out or interact directly with their contributions [6-9]! Best regards, Ian Y. Choi (ianychoi) & Seongsoo Cho (seongsoocho) OpenStack I18n SIG & Student Mentors [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [2] Video - OpenStack I18n Zanata-to-Weblate Migration: Weblate Tools Unit Test Development (CMU Project Demo) (Furqan), link: https://youtu.be/w966IpBCqeE [3] Video - OpenStack I18n Zanata-to-Weblate Migration: Translation Scripts working on Zuul (CMU Project Demo) (Jana), link: https://youtu.be/RcQweOe-vfo [4] Photo of our kick off meeting: https://photos.app.goo.gl/QhNwBusFZjwvTBzi7 [5] Photos of our final mentoring meeting: Final Mentoring Meeting - https://1drv.ms/f/c/6cc85a64cb418204/EljY3AfrnypGrF6EyDZq83MBDZpLTPt-8VPymj… [6] https://review.opendev.org/c/openstack/i18n/+/953745 (by Furqan, review is welcome) [7] https://review.opendev.org/c/openstack/i18n/+/955982 (by Simon, review is welcome) [8] https://review.opendev.org/c/openstack/i18n/+/955439 (by Jana, working in progress) [9] https://review.opendev.org/c/openstack/trove-dashboard/+/952787 (by Jana, merged)

1 0

[neutron] Bug Deputy Jul 14 - Jul 28
by Jakub Libosvar 28 Jul '25

28 Jul '25

Hi, as I didn’t find the bug deputy report from the last week and confirmed by looking at the IRC meeting logs, I’ve skimmed through the bugs of the last 2 weeks to make sure nothing falls through the cracks. There are a few incomplete bugs that require more info from the reporters in order to find the culprit, seems Brian and Rodolof are on top of it. There is one Critical from today and seems it’s clear what is wrong with it and it seems Yatin is looking at it. Thanks Kuba Critical -------- * tobiko jobs failing while download fedora qcow2 image Edit https://bugs.launchpad.net/neutron/+bug/2118902 Yatin seems to be looking into it Fedora 40 image URL has moved, we need to update the URL to fetch Fedora 41 High —--- * test_subport_delete random failure https://bugs.launchpad.net/neutron/+bug/2117405 Functional test that fails sporadically Assigned to Rodolfo * [tobiko] OVN Metadata agent class failing when using OVN agent https://bugs.launchpad.net/neutron/+bug/2118398 Assigned to Rodolfo Patch proposed: https://review.opendev.org/c/x/tobiko/+/955769 * OVN Neutron agent is being registered as OVN Metadata agent https://bugs.launchpad.net/neutron/+bug/2118876 Rodolfo and Yatin are working on it Patch proposed: https://review.opendev.org/c/openstack/neutron/+/955987 Medium ------- * Horizon shows all prefix lengths when creating subnet from subnet pool https://bugs.launchpad.net/neutron/+bug/2116927 Lajos looked at it as it might be related to the SDK migration, unclear if any fix in Neutron is required * [eventlet-removal] Add N535 hacking check to ban eventlet imports https://bugs.launchpad.net/neutron/+bug/2117373 This is to add the check into Neutron tree but later the check itself was questioned as it might be not working as intended * [neutron-tempest-plugin] Test ``test_create_router_update_external_gateways`` failing https://bugs.launchpad.net/neutron/+bug/2117383 Assigned to Miguel * [unmaintained-only] unknown keyword flow_group_id https://bugs.launchpad.net/neutron/+bug/2117477 Assigned to Bence * [OVN] OVN agents should clean up "Chassis_Private" previous tags https://bugs.launchpad.net/neutron/+bug/2118893 Assigned to Rodolfo Patch proposed: https://review.opendev.org/c/openstack/neutron/+/955998 Low —-- * NotFoundException: 404 error when associating FIP with an unreachable network https://bugs.launchpad.net/neutron/+bug/2118360 Incomplete ---------- * VPN Perfect Forward Secrecy (PFS) is deactivated although configured as active https://bugs.launchpad.net/neutron/+bug/2116723 Rodolfo asked the reporter for more details * Performance Tuning for Nested VXLAN Tunnel in OpenStack (OVS Backend) https://bugs.launchpad.net/neutron/+bug/2116837 Brian asked the reporter for more details * OVN: Intermittent metadata failures for SR-IOV VMs https://bugs.launchpad.net/neutron/+bug/2117078 Rodolfo asked the reporter for more details, the root cause is still unknown * neutron-openvswitch-agent crashes on start https://bugs.launchpad.net/neutron/+bug/2117153 Brian asked the reporter for more details, the root cause is still unknown, happened just once

1 0

Ovn ext ports
by engineer2024 26 Jul '25

26 Jul '25

I have marked a chassis as extport host. But when a sriov port is created, it is being claimed by the node from the controller logs, but it is showing up and down in southbound alternatively,. But when the same node is marked as chassis-gw, the sriov port is showing as up in southbound and stable. What's could be the reason for this? Thanks elinux

1 0

[ops][largescale-sig][scientific-sig] Ops Radio Hour on July 25, 2025
by Ildiko Vancsa 25 Jul '25

25 Jul '25

Hi OpenStack community, I'm reaching out to you with a friendly reminder that the next OpenStack Ops Radio Hour[1] is scheduled to happen on __July 25th, 2025 at 1300UTC.__ The call series is a casual setting for operators, engineers, and contributors to come together, share knowledge, and collaborate on the complexities of managing and deploying OpenStack environments. Topics the next gathering will dive into: - OVN Migration +Documentation proposal: https://github.com/mariojmdavid/migrate-to-ovn - (SWIFT) Compliance processes - GPUs - VMware migration - vTPM (live migrations or not?): reboot, start What other topics should we add to the agenda? A few reminders: - The group on the call agreed to try out Matrix as a chat platform for more synchronous communication outside calls + You can access the Matrix room here: https://matrix.to/#/#openstack-ops:opendev.org <https://matrix.to/#/%23openstack-ops:opendev.org> + Further details are here: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… - If you would like to read and catch up on notes from previous calls, you can find them in this etherpad: https://etherpad.opendev.org/p/openstack_ops_radiohour See you on the call on July 25th! Bets Regards, Ildikó [1] https://wiki.openstack.org/wiki/Operations/Meetups

1 1

[PTLs][all] 2026.1 Gazpacho's proposed cycle/release schedule
by Elõd Illés 25 Jul '25

25 Jul '25

Hi, This is just to advertise next cycle's proposed release schedule [1][2]. Feel free to comment on the patch [1] about the timing of milestones, etc. The generated page can also be checked here [2] (though be careful, as this belongs to PS4, so if that is not the latest patch set at the time of looking, then please search for the latest one). [1] https://review.opendev.org/c/openstack/releases/+/954614 [2] https://6b6a75d201a9c42f31a1-68f6595b812925233ee703f28dff66ba.ssl.cf5.rackc… Cheers, Elod Illes irc: elodilles @ #openstack-release

1 0

[Kolla-ansible][epoxy]nova problems at restart
by Franck VEDEL (UGA) 25 Jul '25

25 Jul '25

Hello everyone, I need your help. II will try to explain my problem by providing a lot of information. I have been trying to solve it for 3 days, without success. In May, my old cluster became too small for the 200 students using it, so I started installing a new cluster. Six nodes, three in one data center, three in another. After testing with Bobcat and Caracal (unsatisfactory, with numerous issues, especially with authentication and display in Horizon), I tried Epoxy. I installed everything I needed and tested it. It was a real success. It was very fast in its new configuration, and I thought everything would be ready by September. In May, my old cluster was becoming too small for the 200 students using it, so I started installing a new cluster. 6 nodes, 3 in one data center, 3 in another. After testing with Bobcat and Caracal (unsatisfactory, with numerous issues, especially with authentication and display in Horizon), I tried Epoxy. I installed everything I needed and tested it. It was a real success. It was very fast in its new configuration; I thought everything would be ready by September. At the beginning of July, I was told to shut down everything, due to electrical maintenance in a data center. I shut everything down. 3 days later, I restarted it, and nothing worked anymore. However, it was simply a shutdown/restart of the servers. The problems are with Nova. Here's some information and logs, if you can help me restart the cluster. So Epoxy on Ubuntu 2404. (venv2) user1@ordi1:~/OPENSTACK/INSTALL$ kolla-ansible --version kolla-ansible 20.0.1.dev4 Since nova didn't want to work I did this: (venv2) user1@ordi1:~/OPENSTACK/INSTALL$ kolla-ansible reconfigure -I multinode -t nova ERROR with a task: TASK [nova-cell : Waiting for nova-compute services to register themselves] **************** skipping: [ordi2] skipping: [ordi3] skipping: [ordi4] skipping: [ordi5] skipping: [ordi6] An exception occurred during task execution. To see the full traceback, use -vvv. The error was: json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) fatal: [ordi1]: FAILED! => {"msg": "Unexpected failure during module execution: Expecting value: line 1 column 1 (char 0)", "stdout": ""} I search with Google and find this (BUG2 in the link): https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… But I am in 20.0.1.dev4 There is a lot of logs (with nova)….. total 533340 -rw-r--r-- 1 42436 42436 0 juil. 17 06:42 nova-api.log -rw-r--r-- 1 42436 42436 105512247 juil. 17 06:42 nova-api.log.1 -rw-r--r-- 1 42436 42436 2460643 juil. 6 06:40 nova-api.log.2.gz -rw-r--r-- 1 42436 42436 7305818 juil. 5 06:31 nova-api.log.3.gz -rw-r--r-- 1 42436 42436 7234505 juil. 2 06:48 nova-api.log.4.gz -rw-r--r-- 1 42436 42436 2356307 juin 29 06:35 nova-api.log.5.gz -rw-r--r-- 1 42436 42436 7181854 juin 28 06:49 nova-api.log.6.gz -rw-r--r-- 1 42436 42436 56065234 juil. 18 09:06 nova-api-uwsgi.log -rw-r--r-- 1 42436 42436 113689390 juil. 17 06:42 nova-api-uwsgi.log.1 -rw-r--r-- 1 42436 42436 2150056 juil. 6 06:40 nova-api-uwsgi.log.2.gz -rw-r--r-- 1 42436 42436 6393602 juil. 5 06:31 nova-api-uwsgi.log.3.gz -rw-r--r-- 1 42436 42436 6383183 juil. 2 06:48 nova-api-uwsgi.log.4.gz -rw-r--r-- 1 42436 42436 2083376 juin 29 06:35 nova-api-uwsgi.log.5.gz -rw-r--r-- 1 42436 42436 6351824 juin 28 06:49 nova-api-uwsgi.log.6.gz -rw-r--r-- 1 42436 42436 1467596 juil. 18 09:06 nova-compute.log -rw-r--r-- 1 42436 42436 2626598 juil. 18 09:06 nova-conductor.log -rw-r--r-- 1 42436 42436 44883046 juil. 18 06:45 nova-conductor.log.1 -rw-r--r-- 1 42436 42436 7154 juil. 18 08:58 nova-manage.log -rw-r--r-- 1 42436 42436 221050 juil. 16 15:08 nova-metadata.log -rw-r--r-- 1 42436 42436 28094556 juil. 18 09:06 nova-metadata-uwsgi.log -rw-r--r-- 1 42436 42436 74174166 juil. 17 06:42 nova-metadata-uwsgi.log.1 -rw-r--r-- 1 42436 42436 5650339 juil. 5 06:31 nova-metadata-uwsgi.log.2.gz -rw-r--r-- 1 42436 42436 1861983 juin 29 06:35 nova-metadata-uwsgi.log.3.gz -rw-r--r-- 1 42436 42436 5601477 juin 27 06:53 nova-metadata-uwsgi.log.4.gz -rw-r--r-- 1 42436 42436 5640648 juin 21 06:36 nova-metadata-uwsgi.log.5.gz -rw-r--r-- 1 42436 42436 1871248 juin 15 06:43 nova-metadata-uwsgi.log.6.gz -rw-r--r-- 1 42436 42436 111880 juil. 16 15:08 nova-novncproxy.log -rw-r--r-- 1 42436 42436 2668833 juil. 18 09:06 nova-scheduler.log -rw-r--r-- 1 42436 42436 45997165 juil. 18 06:45 nova-scheduler.log.1 -rw-r--r-- 1 42436 42436 0 mai 15 08:47 privsep-helper.log 2 containers have problems: docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 6231ee0f3c97 quay.io/openstack.kolla/nova-scheduler:2025.1-ubuntu-noble "dumb-init --single-…" 10 minutes ago Exited (1) 5 seconds ago nova_scheduler 57707a9d136e quay.io/openstack.kolla/nova-conductor:2025.1-ubuntu-noble "dumb-init --single-…" 39 hours ago Exited (1) 4 seconds ago nova_conductor Have a look to nova_conductor.log (same thing with nova_scheduler): 2025-07-18 09:08:25.170 7 ERROR nova.scheduler.client.report [-] Failed to initialize placement client (is keystone available?): openstack.exceptions.NotSupported: The placement service for 192.168.100.100:RegionOne exists but does not have any supported versions. 2025-07-18 09:08:25.171 7 ERROR nova.conductor.manager [-] Fatal error initializing placement client: The placement service for 192.168.100.100:RegionOne exists but does not have any supported versions.: openstack.exceptions.NotSupported: The placement service for 192.168.100.100:RegionOne exists but does not have any supported versions. 2025-07-18 09:08:25.172 7 CRITICAL nova [-] Unhandled error: openstack.exceptions.NotSupported: The placement service for 192.168.100.100:RegionOne exists but does not have any supported versions. 2025-07-18 09:08:25.172 7 ERROR nova Traceback (most recent call last): 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/bin/nova-conductor", line 8, in <module> 2025-07-18 09:08:25.172 7 ERROR nova sys.exit(main()) 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/cmd/conductor.py", line 45, in main 2025-07-18 09:08:25.172 7 ERROR nova server = service.Service.create(binary='nova-conductor', 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/service.py", line 256, in create 2025-07-18 09:08:25.172 7 ERROR nova service_obj = cls(host, binary, topic, manager, 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/service.py", line 120, in __init__ 2025-07-18 09:08:25.172 7 ERROR nova self.manager = manager_class(host=self.host, *args, **kwargs) 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/conductor/manager.py", line 124, in __init__ 2025-07-18 09:08:25.172 7 ERROR nova self.compute_task_mgr = ComputeTaskManager() 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/conductor/manager.py", line 255, in __init__ 2025-07-18 09:08:25.172 7 ERROR nova self.report_client 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/conductor/manager.py", line 283, in report_client 2025-07-18 09:08:25.172 7 ERROR nova return report.report_client_singleton() 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/scheduler/client/report.py", line 91, in report_client_singleton 2025-07-18 09:08:25.172 7 ERROR nova PLACEMENTCLIENT = SchedulerReportClient() 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/scheduler/client/report.py", line 237, in __init__ 2025-07-18 09:08:25.172 7 ERROR nova self._client = self._create_client() 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/scheduler/client/report.py", line 280, in _create_client 2025-07-18 09:08:25.172 7 ERROR nova client = self._adapter or utils.get_sdk_adapter( 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/utils.py", line 1035, in get_sdk_adapter 2025-07-18 09:08:25.172 7 ERROR nova return getattr(conn, service_type.replace('-', '_')) 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/openstack/service_description.py", line 88, in __get__ 2025-07-18 09:08:25.172 7 ERROR nova proxy = self._make_proxy(instance) 2025-07-18 09:08:25.172 7 ERROR nova ^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-07-18 09:08:25.172 7 ERROR nova File "/var/lib/kolla/venv/lib/python3.12/site-packages/openstack/service_description.py", line 290, in _make_proxy 2025-07-18 09:08:25.172 7 ERROR nova raise exceptions.NotSupported( 2025-07-18 09:08:25.172 7 ERROR nova openstack.exceptions.NotSupported: The placement service for 192.168.100.100:RegionOne exists but does not have any supported versions. 2025-07-18 09:08:25.172 7 ERROR nova Another thing is strange: Autre point bizarre: tail -f /var/log/kolla/placement/placement-api-uwsgi.log --- no python application found, check your startup logs for errors --- [pid: 1092|app: -1|req: -1/307186] 192.168.100.4 () {22 vars in 215 bytes} [Fri Jul 18 09:11:28 2025] GET / => generated 21 bytes in 0 msecs (HTTP/1.0 500) 3 headers in 102 bytes (0 switches on core 0) What can I do ? Can you help me to find a solution to restart my Openstack ? Thanks a lot if you can. Franck

3 8

[neutron]instances can see traffic of others
by Nguyễn Hữu Khôi 24 Jul '25

24 Jul '25

Hello, I have some instances in the same vlan and compute node. They can see traffic from another instance which looks like port mirror. I can workaround via anti affinity rules but is there any solution for this problem? On vmware we can turn off or on promiscuous mode on the network port group. Thank you. Regards Nguyen Huu Khoi

2 6

[kolla][barbican] How to securely manage OpenStack service passwords with Castellan?
by elnaz cl 24 Jul '25

24 Jul '25

Hi all, I have deployed OpenStack using Kolla Ansible. By default, service passwords (e.g., for MySQL, Keystone, etc.) are stored in clear text inside configuration files rendered by Kolla (such as nova.conf, keystone.conf, etc.). I'm looking for a more secure approach to avoid exposing these secrets. Specifically, is there a way to integrate Barbican and Castellan with Kolla-based deployments, so that secrets can be securely loaded at runtime using oslo.config (e.g., using {{ secret:UUID }})? If this is not natively supported, are there any best practices or workarounds for handling this securely? Thanks in advance for any guidance. Best, [Your Name]

1 0

[neutron] metadata-agents work but are not alive
by Eugen Block 23 Jul '25

23 Jul '25

2 4

Neutron dhcp
by engineer2024 23 Jul '25

23 Jul '25

Hi Folks, In a neutron DHCP network, the route to the link local metadata ip from a VM, is thru the ip set by the neutron dhcp agent's static route option for that subnet. This is the same IP as that of the qdhcp namespace's tap interface. Can we choose a specific ip from this subnet and pass it to neutron to use the same when assigning the ip in qdhcp ns and as a static route option to link local ?

2 1

[Ironic][Plugins] networking-baremetal vs networking-generic-switch
by Joao Antonio 22 Jul '25

22 Jul '25

Hello, team! What is the difference between *networking-generic-switch* and *networking-baremetal* in terms of l*ocal_link_information*? The networking-generic-switch README file is explicit about local_link_information. Does networking-baremetal also handle local_link_information? -- Joao

2 1

[cinder] Disable Availability Zone
by Kees Meijs | Nefos 22 Jul '25

22 Jul '25

Hello Stackers, For legacy purposes, we've got an Availability Zone running that's not to be used for new workload any more. Within Nova one could simply disable Compute Nodes (and that's what we did) ensuring no Compute Instances get scheduled. But, how about Cinder? How can we keep current workload running within a certain AZ, but ensure no new workload gets accepted? Thanks! Cheers, Kees

1 0

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

21 Jul '25

Hello Stackers, We're ten weeks away from the coordinated release of OpenStack 2025.2 ("Flamingo") [1]. The feature freeze date for this release is in five weeks (2025-08-28). In the past week, the OpenStack Technical Committee did not merge any new governance changes, though a few are currently under community review. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee took place on 2025-07-15 over IRC [2]. The TC caught up on a backlog of action items, starting with progress on the community goal to drop the use of eventlet [3]. We discussed the activity within the Monasca project team and have reached out to the PTL and core reviewers to talk about its future. The rest of the meeting focused on the maintenance of the "service-types-authority" repository. While some suggested involving the openstacksdk-core team in its maintenance, others opined that the repo should remain under TC oversight due to its governance significance—since changes affect how services are named and recognized across the ecosystem. For now, we have renewed our commitment to reviewing and merging change proposals more actively. A late tangent about the First Contact SIG’s dormancy prompted an idea to review SIG activity at the upcoming PTG in October. The next meeting of the OpenStack TC is today, 2025-07-22, at 1700 UTC. This meeting will be hosted over IRC on the #openstack-tc channel on OFTC. The agenda has been added to the meeting's wiki page [4]. I hope you'll be able to join us there. Any community member is welcome to edit the wiki page and propose new topics. === Governance Proposals === ==== Open for review ==== - os-test-images never releases | https://review.opendev.org/c/openstack/governance/+/954249 - Retire networking-midonet | https://review.opendev.org/c/openstack/governance/+/955364 - Remove Monasca from active project | https://review.opendev.org/c/openstack/governance/+/953671 - Make Eventlet removal deadlines more acceptable for operators | https://review.opendev.org/c/openstack/governance/+/952903 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 === Upcoming Events === - 2025-07-26: OpenInfra Days, Vietnam: https://www.vietopeninfra.org/void2025 - 2025-08-06: Nominations open for OpenStack elections: https://governance.openstack.org/election/ - 2025-08-26: OpenInfra Days, Korea: https://2025.openinfradays.kr/ - 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/ 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] TC Meeting IRC Log 2025-07-15: https://meetings.opendev.org/meetings/tc/2025/tc.2025-07-15-17.00.html [3] Eventlet removal goal timeline changes: https://review.opendev.org/c/openstack/governance/+/952903 [4] TC Meeting Agenda, 2025-07-22: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

Instance Freeze During Snapshot in OpenStack 2024.1 with Ceph Octopus
by mohammad kokabi 21 Jul '25

21 Jul '25

Hello, I hope this message finds you well. I am currently using OpenStack version 2024.1, with Ceph Octopus as the backend storage. The configuration is as follows: Glance is configured to use the "images" pool on Ceph. The virtual machine disks are stored on the "vms" pool. When I attempt to create a snapshot of a running instance, the instance appears to freeze for a few seconds, during which it loses network connectivity (e.g., I cannot ping it). This behavior is unexpected, as I understand that snapshot operations, especially with Ceph backend, should not significantly interrupt the instance's runtime. Could you please advise what might be causing this issue? Are there any known limitations, configurations, or best practices I should be aware of regarding snapshot behavior with Ceph in this version of OpenStack? Looking forward to your insights. Best regards,

2 1

RE: Create image error
by berndbausch＠gmail.com 21 Jul '25

21 Jul '25

Violating limits imposed by the operator should lead to a useful error message rather than an HTTP 5xx error. In any case, there should have been a message in the Glance API log. Perhaps you are using a prerelease version of OpenStack? When you get Devstack from the Git, you may want to specify the version; otherwise, you obtain software that is currently under development. For example, the following gets you the first version released this year (Epoxy): git clone https://opendev.org/openstack/devstack -b stable/2025.1 ------------------------------------------------------------------------------------------------------------------- From: BEDDA Fadhel <fadhel.bedda(a)gmail.com> Sent: Saturday, May 31, 2025 6:00 PM To: berndbausch(a)gmail.com Subject: Re: Create image error Hello, I was able to work around the problem by disabling the limits in the file: /etc/glance/glance-api.conf False instead of True Thanks Le sam. 31 mai 2025 à 09:55, <mailto:berndbausch@gmail.com> a écrit : My guess is that the image service is down. To check its status: systemctl status devstack@g-api Also check the image service log: journalctl -e -u devstack@g-api ------------------------------------------------------------------------ From: BEDDA Fadhel <mailto:fadhel.bedda@gmail.com> Sent: Saturday, May 31, 2025 3:08 PM To: mailto:openstack-discuss@lists.openstack.org Subject: Create image error Hi everyone, I installed OpenStack (DevStack). At first, I was able to create three images (Ubuntu, Debian, and Windows) in addition to the Cirros image. When I tried to add another image, everything got stuck. I couldn't add any images, and I got the infamous error 550. HttpException: 502: Server Error for url:

1 0

[tacker] Skip today's IRC meeting
by Yasufumi Ogawa 20 Jul '25

20 Jul '25

Hi Tacker team, Sorry for the late notice. Due to a holiday in Japan and most of us will not join, I would like to skip today's IRC meeting. Thanks, Yasufumi

1 0

[kolla-ansible][proxysql] "Wait for backup proxysql container to start" fails
by Bursztynowski Dariusz 20 Jul '25

20 Jul '25

Hello OpenStack community, Installing Kolla-ansible OpenStack 2025.1, I've met a problem with proxysql which does not start (in task [loadbalancer : Wait for backup proxysql to start]) because of unsupported system page size: sudo cat /var/log/kolla/proxysql/proxysql.log <jemalloc>: Unsupported system page size <jemalloc>: Error in malloc(): out of memory I'm working with aarch64 CPU (Raspberry Pi 5 cluster, instructive tool for educational purposes). I have posted the bug here including more detailed description: https://bugs.launchpad.net/kolla-ansible/+bug/2117309 . What is interesting, version 2023.1 works just fine on the same HW/OS platform. I would be grateful for any suggestions on how to resolve this. Best, Dariusz Bursztynowski

1 1

[Nova] Unable to fetch CPU/RAM allocation ratios via /os-hypervisors API (Nova API v2.91 vs v2.1 support)
by Thamanna Farhath 19 Jul '25

19 Jul '25

Hello OpenStack community, I'm working with OpenStack (2023.1 kolla ansible) Nova and using the /os-hypervisors API to gather hypervisor information. I noticed that the CPU and RAM allocation ratios (which are shown in the Horizon dashboard) are not included in the response from: GET /os-hypervisors GET /os-hypervisors/{id} We're currently using Nova API version 2.91, but I see that the /os-hypervisors API appears to support only up to version 2.1, I’d like to clarify the following points: Is it expected behavior that the /os-hypervisors API does not return CPU and RAM allocation ratios? Is there any API endpoint that exposes these ratios programmatically? As we are using Nova API version 2.91, but /os-hypervisors seems limited to v2.1, is this a known limitation or design choice? If the only source of truth is the nova.conf configuration file (e.g., cpu_allocation_ratio, ram_allocation_ratio), is there any plan to expose this via API in future releases? It would be helpful to know if this is something we should work around by manually collecting config values, or if there's a more appropriate method in modern Nova setups. Thamanna Farhath Associate Engineer R&D mailto:manoj.kumar@zybisys.com thamanna.f(a)zybisys.com https://www.zybisys.com https://in.linkedin.com/company/zybisys https://www.facebook.com/Zybisys/ https://www.instagram.com/ZyBiSys/ https://www.youtube.com/@zybisys 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

[mariadb][keystone][blazar] Deadlock error on Galera cluster
by Winicius Allan 18 Jul '25

18 Jul '25

Hi community o/ Suddenly, I noticed that the login on the dashboard wasn't working, so I checked the keystone logs. I saw some entries like that: 2025-07-10 00:53:45.120 23 ERROR sqlalchemy.pool.impl.QueuePool oslo_db.exception.DBDeadlock: (pymysql.err.OperationalError) (1205, 'Lock wait timeout exceeded; try restarting transaction') Nova-conductor was also showing messages like these. At the same time, blazer-manager was logging after every _process_event calling: ERROR sqlalchemy.exc.TimeoutError: QueuePool limit of size 1 overflow 50 reached, connection timed out, timeout 30.00 I do not know if it's related to the _process_event method that batches events concurrently[1], and the DB was locked. Well... I increased the max_pool_size from 1 to 2 on blazar-manager, and that message stops showing. Does anyone know what can cause this deadlock generally? I'd like to ask another question: I have three controllers in my environment. Why do controllers with no active VIP address bind connections on the MySQL port, for example: tcp ESTAB 0 0 10.0.0.105:3306 10.0.0.107:50642 users:(("mariadbd",pid=977010,fd=1089)) [1] https://github.com/openstack/blazar/blob/stable/2024.1/blazar/manager/servi… Best regards.

3 5

[ops] Very basic newby questions
by Leroy Tennison 17 Jul '25

17 Jul '25

I am looking for a solution to automatically move (upon request) running VMs from one hypervisor to another. The current hypervisors are KVM/QEMU. Just looking at the documentation I am becoming overwhelmed. Questions (A URL which directly addresses the question is quite acceptable): Does OpenStack work with existing hypervisors or would existing hypervisors have to be "converted" (somehow) to OpenStack? If it can be used with existing hypervisors, is there a how-to for this specific task (I understand that OpenStack can do many things). If OpenStack can't be used with existing hypervisors, are you aware of solutions for this need? I have looked at ProxMox but it appears to want centralized storage and very fast networks which doesn't match the environment. Thank you for your help.

5 10

[neutron] Drivers meeting canceled Friday, July 18th and 25th
by Brian Haley 17 Jul '25

17 Jul '25

Hello Neutrinos: As discussed in our weekly meeting, I am going to cancel the next two Drivers meetings as there is no agenda and I am on PTO. Just a reminder there are still open specs that need review, list is at [0]. Have a nice weekend/week! -Brian [0] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

[ops][api][all] What are we going to do about pastedeploy usage?
by Stephen Finucane 17 Jul '25

17 Jul '25

oslo.service is going through a lot of churn right now as part of the eventlet migration. We recently noticed that some unrelated WSGI routing code had been inadvertently deprecated, and moved to undeprecate this [1]. In the long-term, however, this code doesn't really belong in oslo.service and should be moved elsewhere. I took a stab at bootstrapping an oslo.wsgi package, and after some hacking I arrived at a dependencies list containing the following: * Paste [2] * PasteDeploy [3] * Routes [4] * WebOb [5] As some of you might know, all of these packages are minimally maintained bordering on unmaintained. I'm not entirely sure we want to want to bootstrap a new project using these libraries as opposed to migrating off of them. My question is this: how important is the pastedeploy framework and the paste.ini files nowadays, particularly for deployers? While their use is relatively consistent across projects (see below), not every service uses them and for those that don't, I personally haven't heard complaints about their absence. Rather than migrating the pastedeploy stuff elsewhere, would it make more sense for affected projects to simply define a static set of middleware (with some config knobs for those we want to be able to enable/disable) and call it a day? Cheers, Stephen PS: This topic came up about 18 months ago [6], but we don't appear to have reached a conclusion. Thus my bringing it up again. [1] https://review.opendev.org/c/openstack/oslo.service/+/954055 [2] https://pypi.org/project/Paste/#history [3] https://pypi.org/project/PasteDeploy/#history [4] https://pypi.org/project/Routes/#history [5] https://pypi.org/project/WebOb/#history [6] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… --- fwict, the following services all rely on this combo to build their own frameworks, with Nova most likely the progenitor in each case (I'm guessing) * Nova * Barbican * Cinder * Designate * Freezer * Glance * Heat * Manila * Monasca * Neutron * Swift * Trove * Vitrage * Watcher The following services do *not* use these libraries: * Cyborg (pecan) * Ironic (pecan) * Keystone (Flask + Flask-RESTful, with some webob) * Magnum (pecan) * Masakari (homegrown framework using webob) * Zaqar (falcon) * Zun (Flask)

3 2

[Kolla] Looking for a Support Provider
by Buddhika S. Godakuru - University of Kelaniya 17 Jul '25

17 Jul '25

Hi All, We are a University in Sri Lanka, and we have a small Openstack (2023.1) deployment using Kayobe. The on-prem cloud is currently operational, but currently there is only one member who has the idea about the design, and implementation of hardware/OS/configuration/network setup. So the management is trying to find an additional entity who can support in an emergency, as well as to avoid being dependant on a single person. Are there any person/institute/person who can support our setup (not day to day activities) in case of service/hardware failure, preferably within Sri Lanka. Thank you -- බුද්ධික සංජීව ගොඩාකුරු Buddhika Sanjeewa Godakuru Systems Analyst/Programmer Information and Communication Technology Centre (ICTC) University of Kelaniya, Sri Lanka, Kelaniya, Sri Lanka. -- **** *University of Kelaniya, Sri Lanka, accepts no liability for the content of this email or for the consequences of any actions taken on the basis of the information provided unless that information is subsequently confirmed in writing. * *If you are not the intended recipient, this email and/or any information it contains should not be copied, disclosed, retained or used by you or any other party, and the email and all its contents should be promptly deleted fully, and the sender informed. * ** ** *E-mail transmissions cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete. * ****

2 1

Re: [cinder] How to retype while maintaining volume usage
by Yuta Kambe (Fujitsu) 16 Jul '25

16 Jul '25

Hi Eugen, Thank you for your reply. I've confirmed that 'rbd sparsify' can increase available space. However, I believe there's room for improvement in the retype implementation. Currently, retyping between Ceph backends causes zero-filling, which unnecessarily consumes time and storage space. This is likely to happen frequently, for example, with retypes between Ceph's HDD and SSD backends, and the Ceph administrator would need to run 'rbd sparsify' frequently. Are there any improvements to the retype implementation being considered in the community? I would also appreciate hearing your opinion on the need for improvement. Best regards,

4 11

[horizon] Cancel weekly meetings on 2025-07-23 and 2025-07-30
by Tatiana Ovchinnikova 16 Jul '25

16 Jul '25

Hello team, I am cancelling the two upcoming weekly meetings since about a half of the members are on PTO. See you all in three weeks, August 6th! With kind regards, Tatiana

1 0

[publiccloud-sig] Chairing Public Cloud SIG
by Kees Meijs | Nefos 16 Jul '25

16 Jul '25

Hi all, Recently Felix Kronlage-Dammers asked for someone to take over chairing the bi-weekly Public Cloud SIG. After giving it some thought, I proposed to continue his legacy from the next round and on. Unless someone would object, I'll be sending out meeting invitations from here on. 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.

3 2

Short Bitergia dashboard outage due to maintenance
by Ildiko Vancsa 16 Jul '25

16 Jul '25

Hi OpenStack community, I’m reaching out to let you know that the OpenStack Bitergia metrics dashboard[1] will be unavailable for a short period of time due to scheduled maintenance, where the underlying OpenSearch cluster will be updated. Details of the downtime: * Start Date: Thursday, July 17th at 10:00 AM CEST (01:00 AM PDT) * End Date: Thursday, July 17th at 12:00 PM CEST (03:00 AM PDT) __During this maintenance window, the dashboard will be inaccessible.__ Thank you for your understanding. Best Regards, Ildikó [1] https://openstack.biterg.io/app/dashboards#/view/Overview

1 0

[publiccloud-sig] Next meeting of Public Cloud SIG - July 16th (tomorrow) at 0700 UTC
by Felix Kronlage-Dammers 15 Jul '25

15 Jul '25

Hi everyone, This upcoming Wednesday (which is tomorrow, July 16th) the next meeting of the publiccloud-sig is going to happen. We’ll be meeting at 0700 UTC here: https://meetpad.opendev.org/publiccloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG Have fun! cheers felix -- Felix Kronlage-Dammers Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

[nova] Information Sharing for Arm CCA Feature (Following 4/8 PTG)
by taketani.ryo＠fujitsu.com 14 Jul '25

14 Jul '25

Thank you for the productive discussion about Arm CCA feature [1] at the PTG on April 8th. > The use case for Arm CCA looks ok. But it is a bit early. It is wise to wait at least libvirt / qemu release to have a "stable" code. > We may want to have a OS distribution version (such as Ubuntu XX.YY) which supports Arm CCA so that users can actually use/test the feature The above information is quoted from the PTG Etherpad [2](L316) summary. I'd like to follow up on these points. I'd like to share relevant information about Arm CCA surrounding components (libvirt, QEMU, OS Distributions(e.g., Ubuntu xx.xx), hardware) as it becomes available, and proceed with the discussion step by step.. I'm starting with this email, but if there's a more appropriate method for sharing this type of information, please let me know. Here's the Arm CCA software components information I can share at this time: * Linux Kernel: The roadmap is outlined on the fifth page of the third attachment in this link [3]. The initial commits I've proposed to OpenStack are focused on RMM 1.0. KVM host support for RMM 1.0 will be available in H2 2025. * QEMU Upstream Status: The development is in-progress, awaiting the Linux Kernel merge * libvirt Upstream Status: The development is in-progress, awaiting the QEMU merge * OS Distribution Support: The road map is not clear now > We may want to have a OS distribution version (such as Ubuntu XX.YY) which supports Arm CCA so that users can actually use/test the feature I have a question regarding the above. For design discussions leading to spec approval, I understand that upstream QEMU/libvirt stable release is necessary. Is a specific OS distribution release (e.g., Ubuntu xx.xx) also required for spec approval? [1] https://review.opendev.org/c/openstack/nova-specs/+/938276 [2] https://etherpad.opendev.org/p/nova-2025.2-ptg [3] https://lists.trustedfirmware.org/archives/list/tsc@lists.trustedfirmware.o… Regards, Ryo Taketani

3 11

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

14 Jul '25

Hello Stackers, We're eleven weeks away from the date of the coordinated release of OpenStack 2025.2 ("Flamingo") [1]. The feature freeze date for this release cycle is 2025-08-28. OpenStack project teams are busy working on and polishing features to meet this deadline. In the past week, we marked the shade and os-client-config packages as deprecated [2]. The functionality provided by these two packages has long been available through openstacksdk. We don't plan to create any new releases for these packages unless critical bugs are discovered. Besides that, there have been no significant governance updates; however, several proposals are under community review. As part of the OpenInfra Foundation's transition under the Linux Foundation, your individual membership must be renewed. The OIF staff have made this a super-easy one-click process [3]. Please complete this by 2025-07-19 to contest or vote in the next OIF Board elections. OpenStack's own PTL and TC elections will occur between 23:45 UTC on 2025-08-27 and 23:45 UTC on 2025-09-17 [4]. To contest or vote in these elections, you must renew your Foundation membership by 00:00 UTC on 2025-08-20. Don't wait—this process only takes a couple of minutes! === Weekly Meeting === The last weekly IRC meeting of the OpenStack TC took place on 2025-07-08 [5]. We noted that consensus is emerging on the updated Eventlet removal timelines [6]. We followed up on the removal of all references to the Contributor License Agreement from governance docs and OpenStack manuals. There may still be some references lurking in various project documentation websites. We request contributors to file bugs or submit simple documentation updates to switch these references to the Developer Certificate of Origin [7]. OpenStack CI jobs saw some multinode hiccups over the week due to bugs in zuul-launcher. These have been resolved by the OpenDev Infra team, and CentOS/Rocky 10 along with Debian Trixie node images are expected to be served by zuul-launcher soon. The proposal to retire Monasca [8] was discussed at length. While the project has been inactive for several cycles, the TC agreed to give maintainers a chance to state their intentions before moving ahead with retirement. We also agreed that we need better visibility into inactive projects for users and operators. We'll be tweaking the appropriate badges that show up on the repositories and adding notices on project documentation websites. Lastly, we were updated that work is underway to fully remove CLA references from Gerrit. The next weekly meeting of the OpenStack TC is on 2025-07-15 at 17:00 UTC. This meeting will be hosted over IRC in OFTC's #openstack-tc channel. Please find the meeting details, including the agenda, on the meeting's wiki page [9]. I hope you'll be able to join us. === Governance Proposals === ==== Merged ==== - Deprecate shade, os-client-config | https://review.opendev.org/c/openstack/governance/+/953549 ==== Open for review ==== - Remove Monasca from active project | https://review.opendev.org/c/openstack/governance/+/953671 - Make Eventlet removal deadlines more acceptable for operators | https://review.opendev.org/c/openstack/governance/+/952903 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - os-test-images never releases | https://review.opendev.org/c/openstack/governance/+/954249 === Upcoming Events === - 2025-07-19: OpenInfra Days, Indonesia: https://2025.openinfra.id/ - 2025-07-26: OpenInfra Days, Vietnam: https://www.vietopeninfra.org/void2025 - 2025-08-06: Nominations open for OpenStack elections: https://governance.openstack.org/election/ === 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 17:00 UTC [9]. 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] Deprecation of shade and os-client-config: https://review.opendev.org/c/openstack/governance/+/953549 [3] Renew OIF membership: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [4] OpenStack Election Schedule: https://summit2025.openinfra.org/a/schedule [5] TC Meeting IRC Log 2025-07-08: https://meetings.opendev.org/meetings/tc/2025/tc.2025-07-08-17.00.html [6] Eventlet removal timeline proposal: https://review.opendev.org/c/openstack/governance/+/952903 [7] DCO instructions: https://docs.openstack.org/contributors/common/dco.html [8] Retiring monasca: https://review.opendev.org/c/openstack/governance/+/953671 [9] TC Meeting Agenda, 2025-07-15: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

Handling VirtualMedia under Systems path (HPE Superdome Redfish)
by Sangle, Pooja 14 Jul '25

14 Jul '25

Hi all, I'm working with HPE Superdome hardware and noticed that their Redfish implementation exposes VirtualMedia under `/redfish/v1/Systems/{id}/VirtualMedia/`, which differs from the common `/Managers/{id}/VirtualMedia/` path expected by sushy and Ironic. HPE confirms this is standard-compliant per Redfish, but Ironic fails to locate the media devices due to this layout. Before opening a bug or patch, is there known support or discussion around handling this variant? Any pointers welcome! Best, Pooja Sangle

3 4

[neutron] Bug report Jul 7 - Jul 13
by Rodolfo Alonso Hernandez 14 Jul '25

14 Jul '25

Hello Neutrinos: This is the bug report for week 28 (Jul 7 - Jul 13). High: * master networking sfc jobs broken as ovs agent crashing ( https://bugs.launchpad.net/neutron/+bug/2116337) Project: networking-sfc. Assigned. Patches: https://review.opendev.org/c/openstack/releases/+/954702 , https://review.opendev.org/c/openstack/networking-sfc/+/954633 Medium: * remote-managed vnic-type binding profile validation error ( https://bugs.launchpad.net/neutron/+bug/2116087) Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/954292 * OVN network metadata is broken if allowed-address is configured using the same IP (https://bugs.launchpad.net/neutron/+bug/2116249) Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/954570 Low: * [Doc][OVN] Precedence of enforcement for QoS resource types in ML2/OVN ( https://bugs.launchpad.net/neutron/+bug/2116317) Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/954911 Incomplete * gateway_port: of NAT configured on logical router: is not a valid distributed gateway port on that router ( https://bugs.launchpad.net/neutron/+bug/2116335) Missing logs. * VPN Perfect Forward Secrecy (PFS) is deactivated although configured as active (https://bugs.launchpad.net/neutron/+bug/2116723) Missing version, reproducer, logs. Regards.

1 0

[neutron] Disable subnet-external-network extension
by Maximilian Stinsky-Damke 11 Jul '25

11 Jul '25

Greetings, Since Neutron 2024.2 (25.0.0), the subnet-external-network extension is loaded by default. This causes subnetworks that are part of external networks to be visible to non-admin users. We found this behavior a bit confusing for regular users, as those subnetworks are often not usable for spawning VMs or creating load balancers. Depending on the number of external subnetworks, dashboards like Networks and Load Balancer Create in Octavia can become cluttered with entries that are effectively unusable for non-admins, as they are intended only for routers and floating IPs. I’ve reviewed the patches mentioned in [1], and as far as I can tell, the new extension is enabled by default with no apparent way to disable it or revert to the previous behavior. Am I missing something? Is there a way to prevent external subnetworks from being shown to non-admin users? [1] https://bugs.launchpad.net/neutron/+bug/2051831 Thanks in advance, Best regards, Max

2 2

[neutron] Drivers meeting canceled Friday, July 11th
by Brian Haley 10 Jul '25

10 Jul '25

Hello Neutrinos: I'm going to cancel tomorrow's drivers meeting as there is currently nothing listed in the agenda. Just a reminder there are still open specs that need review, list is at [0]. Have a nice weekend! -Brian [0] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

[skyline] Request to extend core reviewers team
by Vladimir Kozhukalov 09 Jul '25

09 Jul '25

Hi team, The Skyline project seems to be interesting for many users but the review is slow at the moment. Maybe we could call for more volunteers who are able to spend some of their time for review and extend the project core reviewers team. Opinions are welcome. -- Best regards, Kozhukalov Vladimir

3 2

[neutron] Seeking Advise: Automatic Assignment of Default Neutron QoS Policy in OVN-based OpenStack
by Simon Stephan 09 Jul '25

09 Jul '25

Hi all, we’re currently migrating an OpenStack deployment from a setup using libvirt-based QoS (with per-flavor bandwidth limits) to a newer environment using OVN as the networking backend. In the previous environment, bandwidth limits were enforced via libvirt, and each flavor had an associated QoS configuration. Now with OVN, this approach is no longer viable, and we are evaluating Neutron’s native QoS feature as a replacement. Our goals: * Enforce one default bandwidth limit per project (formerly done via flavor). * Apply a default QoS policy automatically to every new project, without requiring manual intervention. * Allow users to create their own projects via Domain Manager. Current Observations: * Neutron QoS policies must be explicitly associated with ports or networks, and there is no system-wide default or setting it on a domain level * There is no built-in mechanism in Neutron or Keystone to automatically attach a default QoS policy when a new project is created. Our Proposed Solution: We are exploring a solution where we: 1. Listen to project.create events on the RabbitMQ message bus. 2. Automatically assign a shared default QoS policy (defined in our service project and marked as shared=True) to the newly created project. 3. Possibly enforce this via automation, e.g. an event-driven microservice or script that uses openstacksdk. Question to the community: * Has anyone implemented something similar? * Is there an existing feature or plugin to apply a default Neutron QoS policy to all newly created projects or their ports/networks? * Are there better alternatives or architectural considerations we should keep in mind? * Any feedback or suggestions would be greatly appreciated. Regards, Simon

2 1

[Nova] Flavor visibility management
by Masahito Muroi 09 Jul '25

09 Jul '25

Hi Nova team, I wonder there is an official Nova way to manage Flavor's visibility. The is_public flag can manage a flavor is visible to all users or not, but it can't block user to use the flavor. Usecase: - Cloud admin sets up some custom flavor for users, but the custom flavors are not available to all users at beginning. - Cloud user needs to get some approval to use the custom flavor before using the custom flavor. - Cloud system needs to show custom flavor list not approved yet to cloud users. The problem is user can only see flavors which are already gotten approval. If not, they can't see custom flavor's list using flavor list API. It's kind of chicken and egg problem. Flavors being visible to cloud user means the cloud user can create an instance using the visible flavor. best regards, Masahito

2 3

[i18n][infra][horizon] Zanata translation job failures after Python 3.8 deprecation
by Ian Y. Choi 09 Jul '25

09 Jul '25

Hi all, During last week's PTG, the I18n SIG identified Zanata translation job failures for Horizon (and likely related plugins). The root cause appears to be Python 3.8 deprecation on Horizon [1]. Failed jobs have been observed on Zuul [2], and translation proposals were made on Gerrit [3]. Since translation sync on Horizon stable branches is functioning correctly, the error message seems to be related to Python 3.8 deprecation: ERROR: Cannot install -r doc/requirements.txt (line 3) due to conflicting package version dependencies. To address this, I'd like to raise two points: 1/ To resolve the issue, would you support updating translation sync jobs with Bionic-based Zuul jobs by either upgrading to Jammy or modifying the Bionic image to support Python >3.8? 2/ At least me from I18n SIG acknowledges that recognizing these translation job errors was delayed. Moving forward, would it be beneficial to implement periodic (e.g., monthly) reporting on translation job successes and failures? Thank you, /Ian [1] https://docs.openstack.org/releasenotes/horizon/2024.2.html#upgrade-notes [2] https://zuul.opendev.org/t/openstack/builds?job_name=propose-translation-up… [3] https://review.opendev.org/q/owner:proposal-bot+project:openstack/horizon+b…

2 3

Action Required: Renew Your OpenInfra Individual Membership by July 19
by Wes Wilson 08 Jul '25

08 Jul '25

Dear OpenInfra Community, OpenInfra Individual membership is now open and requires your immediate action. Following OpenInfra's integration with the Linux Foundation, all individual members must complete a brief renewal process[1], including agreeing to the OIF Individual Member Program[2] and Community Code of Conduct[3], to maintain their voting rights and board representation under our new governance structure. Why this matters: Only members who complete this process by July 19, 2025 will be eligible to vote in the 2026 Individual Governing Board election. According to the OpenInfra Elections Procedures Policy[4], individual members must become a member at least 180 days before an election to be eligible to vote. Missing this deadline means you will not be able to participate in the 2026 board election. For existing members: Complete the renewal form[1] to maintain your membership status. For new members: This is your opportunity to join as an OIF Individual Member and gain voting rights in the 2026 election. Note: The process takes just a few minutes Log in with your OpenInfraID and confirm the permissions check to view the form OIF Individual membership is completely free This secures your ability to vote in and run for the governing board The 180-day eligibility requirement is firm, so we cannot extend 2026 voting eligibility to anyone who misses the July 19 cutoff. This would compromise the integrity of our 2026 board election process. If you miss this cutoff, you will be able to vote in elections beyond 2026 assuming you maintain eligibility. Your participation has always been vital to OpenInfra's mission. As we enter this new chapter with the Linux Foundation, we need engaged individual members more than ever to help shape the future of open infrastructure. Feel free to reply to this email with any questions or reach out to me (wes(a)openinfra.dev) Thierry (thierry(a)openinfra.dev) or Jonathan (jonathan(a)openinfra.dev) directly. Thank you for your continued participation in the OpenInfra Foundation! Regards, Wes Wilson Chief of Staff OpenInfra Foundation [1] https://openinfra.org/a/renew-membership [2] https://openinfra.org/legal/oif-individual-member-program [3] https://openinfra.org/legal/code-of-conduct [4] https://openinfra.org/legal/election-procedures-policy

1 0

Ceilometer-Container (Kolla-Ansible) dauerhaft unhealthy – veraltete Komponenten
by M P 08 Jul '25

08 Jul '25

Hallo zusammen, wir betreiben ein OpenStack-Setup mit Kolla-Ansible (Ubuntu 22.04, aktuelle Kolla-Master-Images) und beobachten dabei regelmäßig, dass der ceilometer_compute-Container in einen dauerhaft unhealthy-Status fällt. Wir haben versucht, dem Problem über die Logs auf den Grund zu gehen – konnten aber bisher keinen klaren Fehler identifizieren, der das Verhalten erklärt. Der Dienst startet zwar scheinbar normal, bleibt aber aus Sicht von Docker dauerhaft „unhealthy“. *Frage in die Runde:* Könnte das Verhalten damit zusammenhängen, dass Teile von Ceilometer mittlerweile deprecated oder nicht mehr aktiv gepflegt sind (z. B. die Ceilometer API oder bestimmte Agenten)? Oder gibt es bekannte Probleme mit Ceilometer in neueren Kolla-Versionen? Über Rückmeldungen oder Hinweise, wie ihr mit Ceilometer im aktuellen Kolla/OpenStack-Umfeld umgeht, würden wir uns freuen. Viele Grüße Mai-Anh ------------------------- Hi everyone, We're running an OpenStack environment with Kolla-Ansible (Ubuntu 22.04, latest Kolla master images), and we’ve been seeing the ceilometer_compute container frequently stuck in a permanently unhealthy state. We've tried investigating through the logs, but haven’t been able to pinpoint a clear cause. The service appears to start normally, but Docker continues to report it as unhealthy. *Question:* Could this be related to the fact that parts of Ceilometer are now deprecated or no longer actively maintained (e.g., the Ceilometer API or specific agents)? Or are there known issues with Ceilometer in recent Kolla/OpenStack releases? We’d appreciate any insights or suggestions — especially regarding how others are handling Ceilometer in current setups. Best regards, Mai-Anh

1 0

[cinder] not rescanning during VM attach
by Anthony Galica 08 Jul '25

08 Jul '25

Hi all, We have a customer problem where LUNs are not able to be scanned in time by cinder, so the operation fails. We fixed the problem in the "create image from volume workflow" by configuring "num_volume_device_scan_tries" in cinder.conf to a larger value. However, this doesn't appear to work for creating a VM and attaching to it, which still always fails. Any configuration or advice here? Thank you, Anthony

2 1

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

07 Jul '25

Hello Stackers, We're officially in the second half of the OpenStack 2025.2 "Flamingo" release cycle [1]. Starting on 2025-08-06, election officials will begin merging nominations for Project Team Leads for the 2026.1 release cycle and to fill four seats on the OpenStack Technical Committee. If you're interested in leading a project or joining the OpenStack TC, I'd encourage you to submit a nomination through the openstack/election repository [2]. The Call for Proposals soliciting project team updates and Forum sessions at the OpenInfra Summit (17–19 October 2025) in Paris-Saclay will be closing on 2025-07-08 at 23:45 PST [3]. The schedule for the event is live and contains some exciting material [4]. In the past week, the OpenStack Technical Committee didn't merge any significant governance changes. However, some proposals are open for the community's review. === Weekly Meeting === The last weekly meeting of the OpenStack TC was held simultaneously on Video (Meetpad) and IRC (OFTC's #openstack-tc channel) on 2025-07-01. The recording of the meeting was posted to the TC's YouTube channel [5], and meeting notes were logged on IRC [6]. The meeting was brief yet efficient, covering updates on various ongoing initiatives. TC members were glad to see the smooth implementation of the Developer Certificate of Origin (DCO) enforcement, with minimal issues reported and proactive steps taken to manage tooling changes. Key action items from the previous week, such as addressing inactive projects and the Eventlet deprecation, were discussed. We noted progress on Cyborg's potential revitalization through new and returning maintainers. We discussed the critical and impending bug in PBR [7] due to upstream changes in Setuptools. The OpenStack user survey remains open until August [8], and the TC would like broader community participation. Lastly, we made plans for a "meet-and-greet" forum session with the OpenStack TC at the upcoming summit. This would be a valuable opportunity for community engagement and discussion of TC responsibilities. We do hope to have at least half of the current TC at the summit. The next meeting of the OpenStack TC is on 2025-07-07, and will be hosted on the #openstack-tc channel on OFTC at 1700 UTC. Please find the agenda and other details on the meeting's wiki page [9]. I hope you'll be able to join us there! === Governance Proposals === ==== Merged ==== - Remove mentions of CLA in licensing guide | https://review.opendev.org/c/openstack/governance/+/953843 ==== Open for review ==== - os-test-images never releases | https://review.opendev.org/c/openstack/governance/+/954249 - Add service-types-authority to SDK deliverables | https://review.opendev.org/c/openstack/governance/+/953548 - Deprecate shade, os-client-config | https://review.opendev.org/c/openstack/governance/+/953549 - Remove Monasca from active project | https://review.opendev.org/c/openstack/governance/+/953671 - Make Eventlet removal deadlines more acceptable for operators | https://review.opendev.org/c/openstack/governance/+/952903 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 === Upcoming Events === - 2025-07-08: OpenInfra Board meeting: https://board.openinfra.org/ - 2025-07-19: OpenInfra Days, Indonesia: https://2025.openinfra.id/ - 2025-07-26: OpenInfra Days, Vietnam: https://www.vietopeninfra.org/void2025 - 2025-08-06: Nominations open for OpenStack elections: https://governance.openstack.org/election/ 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] Submit a PTL/TC candidacy: https://governance.openstack.org/election/#how-to-submit-a-candidacy [3] CFP for Forums/Project Updates: https://cfp.openstack.org/app/2025summit [4] OpenInfra Summit Schedule: https://summit2025.openinfra.org/a/schedule [5] TC Meeting Video Recording, 2025-07-01: https://youtu.be/eJ03g0w8Ers [6] TC Meeting IRC Log 2025-07-01: https://meetings.opendev.org/meetings/tc/2025/tc.2025-07-01-17.00.html [7] pbr setuptools incompatibility: https://bugs.launchpad.net/pbr/+bug/2107732 [8] Take the OpenStack user survey: https://www.openstack.org/user-survey [9] TC Meeting Agenda, 2025-07-08: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

enabling compress live migration
by Jiatong Shen 07 Jul '25

07 Jul '25

Hello fellows, I am doing some research on accelerating live migration speed for some memory heavy workload, for example databases. Instances running these applications usually have large amounts of ram and high dirty page rate. Compute nodes are equipped with ten-gigabit NICs. We found it is very hard to complete the migration in 30 mins and we have to use force-complete in the end. I found some material saying enabling compression could boost migration speed and would like to try out. So how can I enable compress live migration and are there other suggestions? Thank you very much for the help. -- Best Regards, Jiatong Shen

3 2

[cinder][glance][telemetry][barbican] Deliverables defined in governance but not released yet
by Thierry Carrez 07 Jul '25

07 Jul '25

Hi everyone, The release team latest consistency check revealed a number of deliverables that are defined in the openstack/governance repository but do not have a deliverable file in the openstack/releases repository yet. [cinder] rbd-iscsi-client has been added Jan 2021, never released yet. Should it be removed from governance at some point? [glance] os-test-images has been added July 2024, never released yet. Is it a repository that is not meant to be "released" ? If yes, we can mark it "release-management: none" in governance to avoid flagging it. [telemetry] aetos and grian-ui have been recently added (April, 2025). Do you plan to release them as part of the Flamingo release? If yes we should add deliverable files for them in openstack/releases. [barbican] barbican-ui has been added Oct 2019, never released yet. Should it be removed from governance at some point? Thanks in advance for your answers! -- Thierry Carrez (ttx)

2 1

[neutron] Bug Deputy report Jun 30 - Jul 7
by Oleg Bondarev 07 Jul '25

07 Jul '25

Hello Neutron Team, Bug report for the week of June 30 is below: High: ----- - https://bugs.launchpad.net/neutron/+bug/2115629 - mariadb and centos 9 stream mysql tempest and functional jobs failing - Fix Released: https://review.opendev.org/c/openstack/neutron/+/953768 Medium: ------- - https://bugs.launchpad.net/neutron/+bug/2115776 - Neutron fails to delete records for a VM or FIP when there is A and AAAA records with the same name - Triaged - Unassigned Low: ---- - https://bugs.launchpad.net/neutron/+bug/2115878 - [doc] Document how to manually spawn a WSGI process for debugging purposes - Confirmed - assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2115952 - [OVN][QoS] Allow max-bw only QoS policies to use the OVN policer - In progress: https://review.opendev.org/c/openstack/neutron/+/954137 - assigned to Rodolfo Alonso Undecided: ---------- - https://bugs.launchpad.net/neutron/+bug/2115768 - Mellanox Technologies MT2892 Family [ConnectX-6 Dx] SRIOV using Openstack - No IP inside the VM - Incomplete Thanks, Oleg

1 0

[skyline] Skyline appends v3 in the RC file
by Joao Antonio 07 Jul '25

07 Jul '25

2 3

[skyline] Administrator Page not available for an admin user in another domain
by Joao Antonio 05 Jul '25

05 Jul '25

Hello, When I access skyline using admin@Default I'm able to access the Administrator Page. When I access skyline using taikun@taikun I'm not able to access the Administrator Page. Some idea why? openstack domain show taikun +-------------+----------------------------------+ | Field | Value | +-------------+----------------------------------+ | id | ab2384baf3cc43f7ae1fda0ce7e6ae71 | | name | taikun | | enabled | True | | description | None | | options | {} | +-------------+----------------------------------+ openstack project list --domain taikun +----------------------------------+-----------+ | ID | Name | +----------------------------------+-----------+ | 02c534188ec74a3a89ec530b6d224249 | taikun | +----------------------------------+-----------+ openstack user list --domain taikun +----------------------------------+--------+ | ID | Name | +----------------------------------+--------+ | 659c6b30bbc54f32a7e90b63d92a9d9d | taikun | +----------------------------------+--------+ openstack role add --project taikun --user taikun --project-domain taikun --user-domain taikun admin openstack role assignment list --project taikun --project-domain taikun --names --effective --user taikun --user-domain taikun +---------+---------------+-------+---------------+--------+--------+-----------+ | Role | User | Group | Project | Domain | System | Inherited | +---------+---------------+-------+---------------+--------+--------+-----------+ | admin | taikun@taikun | | taikun@taikun | | | False | | manager | taikun@taikun | | taikun@taikun | | | False | | member | taikun@taikun | | taikun@taikun | | | False | | reader | taikun@taikun | | taikun@taikun | | | False | +---------+---------------+-------+---------------+--------+--------+-----------+ openstack role assignment list --project taikun --project-domain taikun +----------------------------------+----------------------------------+-------+----------------------------------+--------+--------+-----------+ | Role | User | Group | Project | Domain | System | Inherited | +----------------------------------+----------------------------------+-------+----------------------------------+--------+--------+-----------+ | abeef1135b254247b3ed7e82d67a74ff | 659c6b30bbc54f32a7e90b63d92a9d9d | | 02c534188ec74a3a89ec530b6d224249 | | | False | +----------------------------------+----------------------------------+-------+----------------------------------+--------+--------+-----------+ openstack role list +----------------------------------+-------------------------------+ | ID | Name | +----------------------------------+-------------------------------+ | 030aa5e0f28a4e229469478d4bc3a041 | heat_stack_user | | 12c79c14d89a4d9bae40f57f7334430f | load-balancer_observer | | 58f7e34845f946b99d02ad8ceafeabe5 | service | | 6ad502b80f8146fa8bf84ea46ad4f279 | load-balancer_global_observer | | 8176fa996c014ced9ac93e057712baa4 | reader | | 9a61d8d430c944b2b95a3773b472347d | member | | 9babd66862fc4df8922c88311640fee6 | load-balancer_quota_admin | | abeef1135b254247b3ed7e82d67a74ff | admin | | b06622b5167d4f5ca1c08f63f6da3be4 | load-balancer_member | | eb3cf02635894e5d8f80cfc93398520e | load-balancer_admin | | fd01d0c357b64d3da37dd482d80d14f7 | manager | +----------------------------------+-------------------------------+ openstack role assignment list --project admin --project-domain Default --names --effective --user admin --user-domain Default +---------+---------------+-------+---------------+--------+--------+-----------+ | Role | User | Group | Project | Domain | System | Inherited | +---------+---------------+-------+---------------+--------+--------+-----------+ | admin | admin@Default | | admin@Default | | | False | | manager | admin@Default | | admin@Default | | | False | | member | admin@Default | | admin@Default | | | False | | reader | admin@Default | | admin@Default | | | False | +---------+---------------+-------+---------------+--------+--------+-----------+ openstack role assignment list --project admin --project-domain Default +----------------------------------+----------------------------------+-------+----------------------------------+--------+--------+-----------+ | Role | User | Group | Project | Domain | System | Inherited | +----------------------------------+----------------------------------+-------+----------------------------------+--------+--------+-----------+ | abeef1135b254247b3ed7e82d67a74ff | 4eabf78b22254a7f99a34a02c09bd45e | | 0667c5c9c4da4584815880d94f649524 | | | False | | abeef1135b254247b3ed7e82d67a74ff | 659c6b30bbc54f32a7e90b63d92a9d9d | | 0667c5c9c4da4584815880d94f649524 | | | False | | abeef1135b254247b3ed7e82d67a74ff | 659c6b30bbc54f32a7e90b63d92a9d9d | | 0667c5c9c4da4584815880d94f649524 | | | True | | abeef1135b254247b3ed7e82d67a74ff | c2d61ab27c6a4563bb96fa549eae2ee8 | | 0667c5c9c4da4584815880d94f649524 | | | False | +----------------------------------+----------------------------------+-------+----------------------------------+--------+--------+-----------+

3 5

[release] Release countdown for week R-12
by Thierry Carrez 04 Jul '25

04 Jul '25

Development Focus ----------------- We are now past the flamingo-2 milestone, and entering the last development phase of the cycle. Teams should be focused on implementing planned work for the cycle. Now is a good time to review those plans and reprioritize anything if needed based on what progress has been made and what looks realistic to complete in the next few weeks. General Information ------------------- Looking ahead to the end of the release cycle, please be aware of the feature freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (August 21, 2025). 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, 2025) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, August 28, 2025. 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, 2025) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (September 26, 2025) Upcoming Deadlines & Dates -------------------------- Non-client library freeze: August 21, 2025 (R-6 week) Client library freeze: August 28, 2025 (R-5 week) Flamingo-3 milestone: August 28, 2025 (R-5 week) Final 2025.2 "Flamingo" release: October 1st, 2025 OpenInfra Summit Europe: October 17-19, 2025 -- Thierry Carrez (ttx)

1 0

[neutron][octavia] vip port missing virtual-parent in ovn
by Maximilian Stinsky-Damke 03 Jul '25

03 Jul '25

Greetings, I'm currently debugging a strange issue related to Octavia loadbalancer failovers and was wondering if anyone has encountered something similar or has any insights. We're running Neutron with ML2/OVN and the ovn-bgp-agent. When we create Octavia load balancers using the Amphora driver, they come up fine. After attaching a floating IP, the ovn-bgp-agent correctly announces the FIP. However, during load balancer failovers, we sometimes observe that the FIP is no longer being announced. After some debugging, we found that the ovn-bgp-agent stops announcing the FIP because the VIP port in OVN is down and no longer has a neutron:host_id set in external_ids. Digging deeper, we noticed that the VIP port's options:virtual-parents only includes a single port ID and it's not the one corresponding to the current VRRP master. As a result, OVN doesn't associate the VIP with the active amphora, causing the port to be up=false and leaving the external_ids:neutron:host_id field empty. Because of this, no bgp-agent sees itself as responsible for announcing the FIP. Looking at the Octavia amphora ports in Neutron, all of them have the correct allowed address pairs set. This should normally result in the correct virtual-parents being reflected in OVN. Interestingly, I was able to reproduce this behavior even with the SINGLE topology in Octavia, a failover sometimes removes the entire options fields related to virtual-parents and virtual-ip from the VIP port. Manually unsetting and re-setting the allowed address pair on the affected port always restores the correct virtual-parents, and the announcement resumes. Now the question is how could this happen? It seems completely random, but it's very reproducible in my environment. We're running Neutron 2025.1 (26.0.0) with OVN 24.03.1-5.el9. I haven't found any errors in the Neutron server logs indicating issues writing to OVN, or any relevant tracebacks. Thanks in advance for any input or ideas! Best regards, Max

2 3

[cinder] How to retype while maintaining volume usage
by Yuta Kambe (Fujitsu) 02 Jul '25

02 Jul '25

Hi everyone, We are using a Ceph cluster as the backend for Cinder. The Ceph cluster has two pools: volumes_data_hdd for HDDs and volumes_data_ssd for SSDs. These are assigned to the Cinder volume types ceph-hdd and ceph-ssd, respectively. To change the type of a ceph-hdd volume to ceph-ssd, I executed the following command: openstack volume set --type ceph-ssd --retype-policy on-demand <ID of ceph-hdd volume> After execution, checking the capacity with the 'ceph df' command shows an increase in usage after the type change. The following is an example of migrating a newly created, empty 10GB ceph-hdd type volume to ceph-ssd: $ sudo ceph df | grep volumes_data volumes_data_hdd 19 1 98 GiB 25.51k 195 GiB 2.24 4.2 TiB volumes_data_ssd 22 1 91 GiB 23.89k 181 GiB 3.55 2.4 TiB $ openstack volume list --long | grep 7fd16e56-71ec-430b-8499-8d216a57f1c6 | 7fd16e56-71ec-430b-8499-8d216a57f1c6 | test | available | 10 | ceph-hdd | false | | | $ openstack volume set --type ceph-ssd --retype-policy on-demand 7fd16e56-71ec-430b-8499-8d216a57f1c6 $ openstack volume list --long | grep 7fd16e56-71ec-430b-8499-8d216a57f1c6 | 7fd16e56-71ec-430b-8499-8d216a57f1c6 | test | available | 10 | ceph-ssd | false | | | $ sudo ceph df | grep volumes_data volumes_data_hdd 19 1 98 GiB 25.51k 195 GiB 2.24 4.2 TiB volumes_data_ssd 22 1 101 GiB 26.45k 201 GiB 3.95 2.4 TiB Despite the volume being empty, the usage of volumes_data_ssd increases by 10GB. I suspect this is due to zero-filling of unused space during the copy process. Is it possible to change the volume type using Cinder functionality while maintaining the same usage? If not, I think it would be better to use the 'rbd cp' command internally for type changes within Ceph, as it should be able to copy the image while preserving the image size. What are your thoughts on this approach? OpenStack and Ceph versions are: $ ceph -v ceph version 17.2.8 (f817ceb7f187defb1d021d6328fa833eb8e943b3) quincy (stable) $ dnf list --installed | grep openstack-cinder openstack-cinder.noarch 1:21.3.2-1.el9s @centos-openstack-zed Best regards,

2 1

[publiccloud-sig] Next meeting of Public Cloud SIG - July 2nd (today) at 0700 UTC
by Felix Kronlage-Dammers 01 Jul '25

01 Jul '25

Hi everyone, This upcoming Wednesday (which is today, July 2nd) the next meeting of the publiccloud-sig is going to happen. We’ll be meeting at 0700 UTC here: https://meetpad.opendev.org/publiccloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG Sorry for the short notice! Have fun! cheers felix -- Felix Kronlage-Dammers Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

[Nova] - Upgrading to Epoxy causes Ubuntu cloud images to fail DHCP
by Karl Kloppenborg 01 Jul '25

01 Jul '25

Hi Team, We’ve got a weird one where other images (cirros, Debian, fedora etc) work fine. However upgrading to Nova Epoxy ubuntu fails cloud-init because network timed out. Note network loads fine and DHCP is received on cirros etc and setting config-drive for the installation Ubuntu works, and continues to work. It smells of some driver issue/change but I haven’t put my finger on it yet. Boot log: https://gist.github.com/inventionlabsSydney/3d491bb08ea96d1f32ed16fd6b58179a Image was uploaded as such: openstack image create --file ~/noble-server-cloudimg-amd64.img --disk-format qcow2 \ --min-disk 8 \ --min-ram 1024 \ --public \ --property hw_firmware_type=uefi \ --property hw_disk_bus=scsi \ --property hw_scsi_model=virtio-scsi \ --property hw_machine_type=pc-q35-focal-hpb ’Noble Test' Has anyone else seen this yet? 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

Error Occurred After Multipath Configuration
by jiwooo.oh＠samsung.com 01 Jul '25

01 Jul '25

After setting up multipath on netapp, errors occur frequently when detaching a volume. Unexpected error while running command. Command: multipath -f 3600a098038314e7a4b24577351787462 Exit code: 1 Stderr: map in use' This occurs when executing the multipath -f command, and a 'map in use' error occurs. [Full error log] 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] Traceback (most recent call last): 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/virt/block_device.py", line 413, in driver_detach 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] virt_driver.detach_volume(context, connection_info, instance, mp, 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/virt/libvirt/driver.py", line 2860, in detach_volume 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] self._disconnect_volume(context, connection_info, instance, 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/virt/libvirt/driver.py", line 2099, in _disconnect_volume 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] vol_driver.disconnect_volume( 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] File "/var/lib/kolla/venv/lib/python3.10/site-packages/nova/virt/libvirt/volume/iscsi.py", line 74, in disconnect_volume 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] self.connector.disconnect_volume( 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] File "/var/lib/kolla/venv/lib/python3.10/site-packages/os_brick/utils.py", line 174, in trace_logging_wrapper 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] return f(*args, **kwargs) 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] File "/var/lib/kolla/venv/lib/python3.10/site-packages/os_brick/initiator/connectors/base.py", line 78, in inner 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] return f(*args, **kwargs) 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] File "/var/lib/kolla/venv/lib/python3.10/site-packages/os_brick/utils.py", line 415, in change_encrypted 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] res = func(**call_args) 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] File "/var/lib/kolla/venv/lib/python3.10/site-packages/os_brick/initiator/connectors/iscsi.py", line 894, in disconnect_volume 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] return self._cleanup_connection(connection_properties, force=force, 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] File "/var/lib/kolla/venv/lib/python3.10/site-packages/os_brick/initiator/connectors/iscsi.py", line 948, in _cleanup_connection 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] multipath_name = self._linuxscsi.remove_connection( 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] File "/var/lib/kolla/venv/lib/python3.10/site-packages/os_brick/initiator/linuxscsi.py", line 382, in remove_connection 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] self.flush_multipath_device(multipath_name) 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] File "/var/lib/kolla/venv/lib/python3.10/site-packages/os_brick/initiator/linuxscsi.py", line 450, in flush_multipath_device 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] self._execute('multipath', '-f', device_map_name, run_as_root=True, 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] File "/var/lib/kolla/venv/lib/python3.10/site-packages/os_brick/executor.py", line 55, in _execute 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] result = self.__execute(*args, **kwargs) 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] File "/var/lib/kolla/venv/lib/python3.10/site-packages/os_brick/privileged/rootwrap.py", line 172, in execute 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] return execute_root(*cmd, **kwargs) 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] File "/var/lib/kolla/venv/lib/python3.10/site-packages/oslo_privsep/priv_context.py", line 271, in _wrap 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] return self.channel.remote_call(name, args, kwargs, 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] File "/var/lib/kolla/venv/lib/python3.10/site-packages/oslo_privsep/daemon.py", line 215, in remote_call 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] raise exc_type(*result[2]) 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266]oslo_concurrency.processutils.ProcessExecutiON-ERROR: Unexpected error while running command. Jun 4, 2025 @ 05:08:04.928 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] Jun 4, 2025 @ 05:08:04.928 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] Stderr: '9203485.810915 | 3600a098038315143433f58706d524b7a: map in use\n' Jun 4, 2025 @ 05:08:04.928 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] Stdout: '' Jun 4, 2025 @ 05:08:04.928 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] Exit code: 1 Jun 4, 2025 @ 05:08:04.928 1487897 ERROR nova.virt.block_device [instance: 402cec31-5d7e-4167-b057-09675dcf4266] Command: multipath -f 3600a098038315143433f58706d524b7a [Related config] use_multipath_for_image_xfer: true netapp_lun_space_reservation: disabled image_volume_cache_enabled: true image_volume_cache_max_size_gb: 0 image_volume_cache_max_count: 50 [Error Occurrence Case] - Create volume with image - Volume detach - Stop then start operation - vm resize Is there a solution to this situation?

1 0

[heat][ops] Removal of standalone api services (heat-api and heat-cfn-api)
by Takashi Kajinami 01 Jul '25

01 Jul '25

Hello, Historically heat has provided two methods to deploy api services (native heat api and heat CFN api). 1. standalone script based on eventlet 2. wsgi application run by server framework like apache or uwsgi Now the heat team is trying to get rid of eventlet following the global effort to replace it, and the current blocker is 1 because we have no good alternative to re-implement the standaloe service. The global migration strategy is to remove standalone api services using eventlet and provide only wsgi application. So I'm now sending an email to ask for any input, in case if any operator has concern about our current plan below. - Backport deprecation of standalone api scripts to 2025.1 - Remove these scripts during 2025.2 This means that any operators should use 3rd party server framework like uwsgi and apache+mod_wsgi to run heat api from 2025.2 . I understand backporting deprecation is something we won't accept usually, but I've seen this pattern was done in the past for a few exceptions like Hyper-V support removal. If we hear no objections/concerns for a week then, we aim to merge the removal during this cycle. Thank you, Takashi -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

1 1