October 2025 - openstack-discuss - lists.openstack.org

[glance] image upload fails "Unsupported Media Type", "Multiple formats detected: iso,gpt"
by Eugen Block 13 Oct '25

13 Oct '25

Good morning, after our recent upgrade to Epoxy we had troubles uploading images to Glance: openstack image create --disk-format raw --file .../opensuse/Leap-16.0-offline-installer-x86_64.install.iso --progress --public test-ebl [=============================>] 100% HttpException: 415: Client Error for url: http://controller.domain:9292/v2/images/e23d802e-d927-4f34-ae2d-1d6f54d6206…, Unsupported Media Type And in the logs this is reported: 2025-10-11 01:16:56.585 65675 ERROR glance.api.v2.image_data [None req-086ad005-a455-471a-bb0d-9dfe5e27eacf 89c5dcc8793d4867bae22d50e51e16b3 90c403f317ee47feb0dad58461e76fb1 - - default default] Multiple formats detected: iso,gpt: glance.common.exception.InvalidImageData: Multiple formats detected: iso,gpt This is the official openSUSE Leap 16 ISO file. For now I disabled the check by setting: [image_format] require_image_format_match = false The docs state that this is likely a bug: > Disabling this may be required in the case of false match (or > mismatch) issues, but those are bugs that should be filed and fixed. I tried a couple of different ISO files (Ubuntu, openSUSE, incl. older files), all fail with the same error. Uploading raw images seemed to work fine. ISOs are supported file formats according to the docs, could anyone shed some light on this? Thanks! Eugen

2 6

[neutron] Bug deputy Oct 6 - Oct 12
by Rodolfo Alonso Hernandez 13 Oct '25

13 Oct '25

Hello Neutrinos: This is the bug report from the last week (Oct 6 - Oct 12) High: * [VPNAAS] vpnaas AttributeError: 'dict' object has no attribute 'router' ( https://bugs.launchpad.net/neutron/+bug/2127169) Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron-vpnaas/+/963493 * [VPNAAS] vpnaas no config update in ipsec.conf ( https://bugs.launchpad.net/neutron/+bug/2127166) Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron-vpnaas/+/963490 * [VPNAAS] Libreswan config broken when used with new AEAD ciphers ( https://bugs.launchpad.net/neutron/+bug/2127159) Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron-vpnaas/+/963489 * [VPNAAS] ovn-vpn-agent fails to delete vpn service ( https://bugs.launchpad.net/neutron/+bug/2127157) Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron-vpnaas/+/963487 * OVN CI jobs on ironic are broken ( https://bugs.launchpad.net/neutron/+bug/2127038) Assigned. Patch proposed: https://review.opendev.org/c/openstack/neutron/+/963390 (fixed). Medium: * ovn_dhcp4_global_options doesn't support keys with a list of values ( https://bugs.launchpad.net/neutron/+bug/2126923) Not assigned. Undecided: * Neutron not able to create external ports for virtual routers ( https://bugs.launchpad.net/neutron/+bug/2126913) Still deciding if this is a configuration issue. Regards.

1 0

Unable to create new instance while the computes are up
by Ahmad Milad Pour 13 Oct '25

13 Oct '25

Hello there, I asked the ChatGPT to help me to install the openstack on region, and to run a compute server. The ".sh" files are the installation. The "common_ask.sh" file is I run on both servers. The "region_ask.sh" is the file to install openstack and the region. The "compute_ask.sh" is the file to run the compute. The logs and errors are in the "region_details.txt" file. Would you please help me why the server I create has error and cannot be up? The way to create new instance is in the last lines of the "region_ask.sh" which is "openstack server create ...". Regards Ahmad

4 3

[tacker] Cancelling weekly IRC meeting
by Yasufumi Ogawa 12 Oct '25

12 Oct '25

Hi team, Due to a holiday and most of the core members aren't join, I'm cancelling tomorrow's meeting. Regards, Yasufumi

1 0

[OpenStack Ansible] [Deployment] Networking design
by holywine＠outlook.com 12 Oct '25

12 Oct '25

Hello, I am trying to build a minimum usable production-level cloud with OpenStack Ansible following online reference. The idea it shoud be able to scale up without radical change afterwards. Online reference: https://docs.openstack.org/project-deploy-guide/openstack-ansible/2025.1/ openstack-ansible version: stable/2025.1 Target hosts (Ubuntu 24.04LTS): 1) Infra1: Controller 1 + networking 2) Infra2: Controller 2 3) Compute 1: Compute 1 + storage 1 4) Compute 2: Compute 2 + storage 2 Deploy host: dev-host (Ubuntu 24.04LTS) Network: Each sever has two network adapter, say enp11s0f0 and enp11s0f1 (different server may have different port name, en0 and en1 for short). Public IP (en1) : Infra1 - 10.2.46.70/24, fixed IP permanently assigned by provider. Infra2, Compute 1, Compute 2 - 10.2.46.XX/24, dynamic IP temporary assigned for SW installation Private IP (en0): Infra1: 172.29.236.11/22, VLAN 10 172.29.240.11/22, VLAN 30 Infra2: 172.29.236.12/22, VLAN 10 172.29.240.12/22, VLAN 30 Compute 1: 172.29.236.13/22, VLAN 10 172.29.240.13/22, VLAN 30 172.29.244.13/22, VLAN 20 Compute 2: 172.29.236.14/22, VLAN 10 172.29.240.14/22, VLAN 30 172.29.244.14/22, VLAN 20 VLAN 10 - management network VLAN 30 - tunnel network VLAN 20 - storage network Target: Since only Infra1:en1 is available with fixed public IP, It would be the only Internet connection without any port bonding. What have been done: 1) All ordinary IPs and VLANs setting (as above Network part) - The settings are verified and working (verified by ping and curl) 2) user_variables.yml haproxy_keepalived_external_vip_cidr: "10.2.46.70/24" haproxy_keepalived_internal_vip_cidr: "172.29.236.11/22" haproxy_keepalived_external_interface: enp11s0f1 haproxy_keepalived_internal_interface: br-mgmt 3) openstack_user_config.yml internal_lb_vip_address: 172.29.236.11 external_lb_vip_address: 10.2.46.70 Based on experiences as network engineer previously and a lot of readings from books and online guidance esp. the OpenStack Ansible deployment reference, I understand there should/could be something extra to be done. Can anybody please give me a clue on what else to be done or it is enough to make it working? Sorry for disturbing if any but netwoking seems to be the most complicated part for OpenStack deployment. The online examples are hard to be comprehend and customized. One small example: Ubuntu seems to be promoting netplan, while the examples are all with /etc/network/interfaces file (difficult to adapte with Ubuntu24.04). Thanks a lot for help in advance!

2 4

[release] Release countdown for week R-24
by Thierry Carrez 10 Oct '25

10 Oct '25

Welcome back to the release countdown emails! These will be sent at major points in the 2026.1 "Gazpacho" development cycle, which should conclude with a final release on April 1st, 2026 (not a joke). Development Focus ----------------- At this stage in the release cycle, focus should be on planning the 2026.1 "Gazpacho" development cycle, assessing Gazpacho community goals and approving Gazpacho specs. General Information ------------------- The 2026.1 "Gazpacho" development cycle will be a classic 26-week-long cycle. In case you haven't seen it yet, please take a look over the schedule for this release: https://releases.openstack.org/gazpacho/schedule.html By default, the team PTL is responsible for handling the release cycle and approving release requests. This task can (and probably should) be delegated to release liaisons. Now is a good time to review release liaison information for your team and make sure it is up to date: https://opendev.org/openstack/releases/src/branch/master/data/release_liais… By default, all your team deliverables from the 2025.2 "Flamingo" release are continued in 2026.1 "Gazpacho" with a similar release model. Upcoming Deadlines & Dates -------------------------- OpenInfra Summit Europe: October 17th-19th, 2025 OpenStack PTG (virtual): October 27th-31st, 2025 Gazpacho-1 milestone: November 13th, 2025 -- Thierry Carrez (ttx)

1 0

[neutron] Drivers meeting canceled Friday, October 10th
by Brian Haley 09 Oct '25

09 Oct '25

Hello Neutrinos: I am going to cancel tomorrow's Drivers meeting as there are no topics and I will be out. At this point we should probably just add things to the PTG etherpad and discuss there [0]. Just a reminder there are still open specs that need updates and/or review, list is at [1]. Have a nice weekend! -Brian [0] https://etherpad.opendev.org/p/oct2025-ptg-neutron [1] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

[PTLs] [OpenStack TC] Anonymized User Survey Feedback
by Jimmy McArthur 09 Oct '25

09 Oct '25

As you know each year we conduct an OpenStack User Survey. A big chunk of that survey data is dedicated to OpenStack projects, WGs, etc… I’d like to invite you all to review the anonymized feedback from 2025[1]. Please review not only for feedback, but to determine if you want to update your TC, PTL or WG questions. Additionally, if the TC can ensure that questions are up to date wrt to project or working group status. For example, we know the InteropWG has been disbanded as of this year, so we should probably remove those questions for 2026. We would like to have ALL reviews/requests in no later than December 1, 2025. If we do not hear from your project, we will assume you want no changes. If you have any questions, please let myself or Allison Price know. Cheers, Jimmy [1] https://docs.google.com/spreadsheets/d/1bte_k0R3_rVzFF9ND5zTZV0j9liXI1PxPNo…

2 2

[neutron] oslo.messaging and port notifications broadcast
by Thomas Goirand 09 Oct '25

09 Oct '25

Hi, Is it possible, with oslo.messaging, to have 3 daemons to get the Neutron port.{create,update,delete}.end notification events? I tried hard, but no mater how I do it, only one of my 3 daemons get the message. I'm about to add forwarding feature to the other 2 when one receives an event. Is there a better way? Cheers, Thomas Goirand (zigo)

5 12

[PTL][release][stable] 2024.1 Caracal transition to Unmaintained
by Elõd Illés 08 Oct '25

08 Oct '25

Hi teams, As 2025.2 Flamingo was released last week and we are in a less busy period, now is the good time to call your attention to the following: At the end of October 2024.1 Caracal is planned to transition to Unmaintained phase [1] (planned date: 2025-10-24). I have generated the list of the current *open* and *unreleased* changes in stable/2024.1 for every repositories [2] (where there are such patches). These lists could help the teams who are planning to do a *final* release on Caracal before moving stable/2024.1 branches to unmaintained/2024.1. Feel free to edit and extend these lists to track your team's progress! Note that the last hash on stable/2024.1 branch will be tagged ('2024.1-eom' tag) and transition patches will be generated soon. After the tagging and cutting unmaintained/2024.1 branch, the new unmaintained branch will be open to for bug fixes, but there won't be official releases for 2024.1 Caracal anymore. (You can get some information about the Unmaintained state on stable policy page [3]). *NOTE*: teams, please focus on wrapping up your libraries first if there is any concern about the changes, in order to avoid broken (final!!) releases! [1] https://releases.openstack.org/ [2] https://etherpad.opendev.org/p/2024.1-caracal-final-release-before-eom [3] https://docs.openstack.org/project-team-guide/stable-branches.html#unmainta… Thanks, Előd Illés irc: elodilles @ #openstack-release

1 0