May 2025 - openstack-discuss - lists.openstack.org

[openstack-ansible] [Antelope]operating upgrade from ubuntu 20 to ubuntu 22 on infra nodes
by Danish Khan 27 May '25

27 May '25

Dear Team, I am trying to upgrade Operating system of Infra node from ubuntu 20 to ubuntu 22. And I am following below docs for same: https://docs.openstack.org/openstack-ansible/2023.1/admin/upgrades/distribu… When I run: openstack-ansible setup-hosts.yml --limit localhost,reinstalled_host* I thought it would upgrade OS of LXC containers as well. I can see ubuntu-22-amd64 in /var/lib/lxc/ and /var/lib/machines/ I can see ubuntu-22-amd64 even when I run lxc-ls command. Should I destroy and recreate lxc containers one by one to upgrade it to ubuntu 22? or is there any playbook which can take care of this? Regards, Danish Khan

2 1

[OpenStack Kolla] Unable to upload image from Horizon
by ankit1999raikwar＠gmail.com 26 May '25

26 May '25

Hello All, We have deployed the latest version of the OpenStack using the Kolla-ansible deployment. Issue description: When we are uploading image from the horizon dashboard using the with the privilege of admin or any other normal user getting below error. we are using the ceph storage as the backend. Error: Type Error: response is undefined and Unable to create Image Details: 1. From CLI I'm able to Upload the image 2. From Horizon getting Error Command Line Interface openstack image create cirros-01 --disk-format qcow2 --file cirros-0.6.2-x86_64-disk.img Output: +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | checksum | c8fc807773e5354afe61636071771906 | | container_format | bare | | created_at | 2025-05-26T05:03:04Z | | disk_format | qcow2 | | file | /v2/images/f4bba9a3-8640-4162-b9de-0b7e29d32dcf/file | | id | f4bba9a3-8640-4162-b9de-0b7e29d32dcf | | min_disk | 0 | | min_ram | 0 | | name | cirros-01 | | owner | 302edafdf0114b41acad32725668cd13 | | properties | os_hash_algo='sha512', | | | os_hash_value='1103b92ce8ad966e41235a4de260deb791ff571670c0342666c8582fbb9caefe6af07ebb11d34f44f8414b609b29c1bdf1d72ffa6faa39c88e8721d09847952b', | | | os_hidden='False', owner_specified.openstack.md5='', owner_specified.openstack.object='images/cirros-01', owner_specified.openstack.sha256='', stores='rbd' | | protected | False | | schema | /v2/schemas/image | | size | 21430272 | | status | active | | tags | | | updated_at | 2025-05-26T05:03:05Z | | virtual_size | 117440512 | | visibility | shared | +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------+ openstack image list +--------------------------------------+-----------+--------+ | ID | Name | Status | +--------------------------------------+-----------+--------+ | 6b92f1ae-9726-469b-a350-f116c36e61d7 | cirros | active | | f4bba9a3-8640-4162-b9de-0b7e29d32dcf | cirros-01 | active | +--------------------------------------+-----------+--------+ From CLI images getting created from cli but we have notice from horizon we are getting error but also in the backend image getting queued. (kolla-venv) root@controller-01:~# openstack image list +--------------------------------------+-----------+--------+ | ID | Name | Status | +--------------------------------------+-----------+--------+ | 5f030764-af42-437d-b6ee-670218a0c4e4 | ankit | queued | | 0195c152-f2b7-42f1-91b4-5e65f7588889 | ankit | queued | | 6b92f1ae-9726-469b-a350-f116c36e61d7 | cirros | active | | f4bba9a3-8640-4162-b9de-0b7e29d32dcf | cirros-01 | active | +--------------------------------------+-----------+--------+ Queued Image (kolla-venv) root@controller-01:~# openstack image show 5f030764-af42-437d-b6ee-670218a0c4e4 +------------------+------------------------------------------------------+ | Field | Value | +------------------+------------------------------------------------------+ | container_format | bare | | created_at | 2025-05-26T05:45:02Z | | disk_format | qcow2 | | file | /v2/images/5f030764-af42-437d-b6ee-670218a0c4e4/file | | id | 5f030764-af42-437d-b6ee-670218a0c4e4 | | min_disk | 0 | | min_ram | 0 | | name | ankit | | owner | 302edafdf0114b41acad32725668cd13 | | properties | os_hidden='False' | | protected | False | | schema | /v2/schemas/image | | status | queued | | tags | | | updated_at | 2025-05-26T05:45:02Z | | visibility | shared | +------------------+------------------------------------------------------+ Active Image (kolla-venv) root@controller-01:~# openstack image show 6b92f1ae-9726-469b-a350-f116c36e61d7 +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | checksum | c8fc807773e5354afe61636071771906 | | container_format | bare | | created_at | 2025-05-26T05:02:02Z | | disk_format | qcow2 | | file | /v2/images/6b92f1ae-9726-469b-a350-f116c36e61d7/file | | id | 6b92f1ae-9726-469b-a350-f116c36e61d7 | | min_disk | 0 | | min_ram | 0 | | name | cirros | | owner | 302edafdf0114b41acad32725668cd13 | | properties | os_hash_algo='sha512', | | | os_hash_value='1103b92ce8ad966e41235a4de260deb791ff571670c0342666c8582fbb9caefe6af07ebb11d34f44f8414b609b29c1bdf1d72ffa6faa39c88e8721d09847952b', | | | os_hidden='False', owner_specified.openstack.md5='', owner_specified.openstack.object='images/cirros', owner_specified.openstack.sha256='', stores='rbd' | | protected | False | | schema | /v2/schemas/image | | size | 21430272 | | status | active | | tags | | | updated_at | 2025-05-26T05:02:03Z | | virtual_size | 117440512 | | visibility | shared | +------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------+ Please find the horizon logs also 2025-05-26 04:53:24.723082 /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_policy/policy.py:1133: UserWarning: Policy "modify_image": "rule:context_is_admin or (role:member and project_id:%(project_id)s)" failed scope check. The token used to make the request was domain scoped but the policy requires ['project'] scope. This behavior may change in the future where using the intended scope is required 2025-05-26 04:53:24.723167 warnings.warn(msg) 2025-05-26 04:53:24.732065 /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_policy/policy.py:1133: UserWarning: Policy "reactivate": "rule:context_is_admin or (role:member and project_id:%(project_id)s)" failed scope check. The token used to make the request was domain scoped but the policy requires ['project'] scope. This behavior may change in the future where using the intended scope is required 2025-05-26 04:53:24.732130 warnings.warn(msg) 2025-05-26 04:53:34.669166 /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_policy/policy.py:1133: UserWarning: Policy "os_compute_api:os-simple-tenant-usage:show": "rule:project_reader_or_admin" failed scope check. The token used to make the request was domain scoped but the policy requires ['project'] scope. This behavior may change in the future where using the intended scope is required 2025-05-26 04:53:34.669253 warnings.warn(msg) 2025-05-26 04:53:34.670620 /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_policy/policy.py:1133: UserWarning: Policy "os_compute_api:os-quota-sets:update": "rule:context_is_admin" failed scope check. The token used to make the request was domain scoped but the policy requires ['project'] scope. This behavior may change in the future where using the intended scope is required 2025-05-26 04:53:34.670653 warnings.warn(msg) 2025-05-26 04:54:01.749398 /var/lib/kolla/venv/lib/python3.12/site-packages/openstack_dashboard/api/keystone.py:408: DeprecationWarning: Using the 'project' argument is deprecated in version '1.7.0' and will be removed in version '2.0.0', please use the 'default_project' argument instead 2025-05-26 04:54:01.749516 users = keystoneclient(request, admin=True).users.list(**kwargs) 2025-05-26 04:54:28.131860 /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_policy/policy.py:1133: UserWarning: Policy "deactivate": "rule:context_is_admin or (role:member and project_id:%(project_id)s)" failed scope check. The token used to make the request was domain scoped but the policy requires ['project'] scope. This behavior may change in the future where using the intended scope is required 2025-05-26 04:54:28.131939 warnings.warn(msg) 2025-05-26 04:54:33.886717 Project switch successful for user "admin". 2025-05-26 04:54:44.853694 Forbidden: /api/glance/images/4b2517db-1352-45ed-ae87-5a6179bc3422/actions/reactivate 2025-05-26 04:54:51.522777 /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_policy/policy.py:1133: UserWarning: Policy "deactivate": "rule:context_is_admin or (role:member and project_id:%(project_id)s)" failed scope check. The token used to make the request was domain scoped but the policy requires ['project'] scope. This behavior may change in the future where using the intended scope is required 2025-05-26 04:54:51.522876 warnings.warn(msg) 2025-05-26 04:55:07.647877 Project switch successful for user "admin". 2025-05-26 04:55:09.798541 OPENSTACK_IMAGE_BACKEND has a format "" unsupported by glance 2025-05-26 04:55:09.798708 OPENSTACK_IMAGE_BACKEND has a format "docker" unsupported by glance 2025-05-26 04:55:09.798760 OPENSTACK_IMAGE_BACKEND has a format "ova" unsupported by glance 2025-05-26 05:03:59.763647 /var/lib/kolla/venv/lib/python3.12/site-packages/oslo_policy/policy.py:1133: UserWarning: Policy "communitize_image": "rule:context_is_admin or (role:member and project_id:%(project_id)s)" failed scope check. The token used to make the request was domain scoped but the policy requires ['project'] scope. This behavior may change in the future where using the intended scope is required 2025-05-26 05:03:59.763801 warnings.warn(msg) Please help to solve this issue. also I don't see any issue or error in the glance api logs

2 2

[neutron] Bug deputy report (week starting on May 19)
by Elvira Garcia Ruiz 26 May '25

26 May '25

Hi folks! Here you have the list of bugs reported for Neutron during last week. It’s been a busy week. There are a couple of them that I left undecided since I don’t feel knowledgeable enough about the issue. We can discuss them at the team meeting if that's ok. (19 May - 25 May) Critical --------- - https://bugs.launchpad.net/neutron/+bug/2111262 [wntp] test_attach_qos_port_to_vm_with_another_port should create VMs on different computes Fix merged by Eduardo Olivares https://review.opendev.org/c/x/whitebox-neutron-tempest-plugin/+/950296 High ------ - https://bugs.launchpad.net/neutron/+bug/2111272 security group delete fails with PgDelCommand.*exceeded timeout 180 seconds, cause: Result queue is empty Unassigned - https://bugs.launchpad.net/neutron/+bug/2111414 [eventlet-removal] Remove the usage of eventlet in unit tests Fix proposed by Rodolfo https://review.opendev.org/c/openstack/neutron/+/950502 - https://bugs.launchpad.net/neutron/+bug/2111417 [eventlet-removal] Remove the usage of eventlet in functional tests Fix proposed by Rodolfo https://review.opendev.org/c/openstack/neutron/+/950521 - https://bugs.launchpad.net/neutron/+bug/2111422 [eventlet-removal] Remove the usage of eventlet in fullstack tests Unassigned - https://bugs.launchpad.net/neutron/+bug/2111498 [OVN] Mechanism driver fails to fix router_ports: KeyError 'neutron:provnet-network-type' Unassigned. Set this as high but I would like to have someone else take a look at this one. - https://bugs.launchpad.net/neutron/+bug/2111593 [ovn] Race between FIP NAT entry creation and OVN port status update Fix proposed by Dmitrii Shcherbakov https://review.opendev.org/c/openstack/neutron/+/950757 Medium ----------- - https://bugs.launchpad.net/neutron/+bug/2111475 openstack network agent list cannot return new added metadata agent Fix proposed https://review.opendev.org/c/openstack/neutron/+/950624 (needs to be proposed on master) - https://bugs.launchpad.net/neutron/+bug/2111572 [OVN] OVN ML2 mech driver forces port update to networking generic switch (NGS) on OVS restart Unassigned - https://bugs.launchpad.net/neutron/+bug/2111584 Failed to get list of ports due to removed network Unassigned. I set it as low hanging fruit since the issue is quite spotted already. Low ------ - https://bugs.launchpad.net/neutron/+bug/2111330 [FT] Error in ``test_pb_type_empty`` test Unassigned Wishlist ----------- - https://bugs.launchpad.net/neutron/+bug/2111276 [RFE] Integrate OVN BGP capabilities into Neutron OVN driver Unassigned. Should be discussed in the drivers meeting. Undecided --------------- - https://bugs.launchpad.net/neutron/+bug/2111254 [ovn] distributed fip missing external_mac Unassigned. I asked froyo if he could take a look at this since the reporter encountered this on an env with octavia. - https://bugs.launchpad.net/neutron/+bug/2111496 Neutron port stuck in DOWN state after update router external connectivity Unassigned - https://bugs.launchpad.net/neutron/+bug/2111660 OVN_AGENT_NEUTRON_SB_CFG_KEY doesn't set when Neutron OVN Agent starts Unassigned Best regards, Elvira

1 0

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

26 May '25

Hello Stackers, We're 18 weeks away from the release date for OpenStack 2025.2 "Flamingo" [1]. Next week is the deadline for "cycle-trailing" [2] projects to tag their 2025.1 "Epoxy" deliverables. Elsewhere, service project teams are busy wrapping up design specifications for features expected to be implemented in this release cycle. A call to action regarding the cross-community goal on "eventlet removal" was made to this mailing list [3]. Please join the #openstack-eventlet-removal channel on OFTC and participate in the effort. Several OpenStack governance changes are currently underway. A major proposal among them is a transition [4] from the Contributor License Agreement (CLA) [5] to the Developer Certificate of Origin [6]. This change will affect every OpenStack contributor. The OpenStack Technical Committee is working with the OpenInfra Foundation and the OpenDev Infrastructure teams to enforce DCO compliance starting 2025-07-01. Please take some time to consider its implications and provide your opinions on the TC resolution [4]. Project maintainers are not expected to reject patches with DCO compliance today. If you spot a "Signed-off-by" in the commit message, there's a good chance reviewers have just looked past this, as it wasn't required so far. It's a good time to review what may be necessary and be prepared for the upcoming change [7]. === Weekly Meeting === The weekly IRC meeting of the OpenStack Technical Committee occurred on 2025-05-20 [8]. An action item regarding relinquishing the "quantum" name on PyPI was discussed. The resolution in this regard was acknowledged by the requester and merged shortly after. The OpenDev infra administrators deleted OpenStack artifacts and handed over the project namespace. The majority of the meeting later focused on the transition from CLA (Contributor License Agreement) to DCO (Developer Certificate of Origin). This move is part of a broader transition into the Linux Foundation, with an effective date of June 1, 2025. The TC needed to reconfirm its desire to move to DCO, preferably within the next two weeks, as the previous resolution on this topic was from 2014. A new resolution confirming the board's recommendation was deemed helpful for community feedback. We discussed many aspects of this transition—a key concern being the smoothness of the transition for contributors. While the technical implementation (Gerrit enforcing Signed-Off-By in commit messages and turning off CLA enforcement) is relatively simple, the human and organizational impact is not trivial. The short timeline for the switchover was a major point of contention, as downstream organizations may need to re-engage legal teams and update internal contribution policies. The possibility of having multiple CLAs active in Gerrit (allowing existing contributors to continue under the old CLA while new contributors use a new CLA for the new entity) was raised as a potential solution to mitigate the immediate impact of the short deadline. However, mixing CLA and DCO enforcement was generally seen as undesirable and hard to implement. Post-meeting, the resolution was proposed [4], and the timeline for implementation has been pushed out by a month to allow the community time to prepare and react accordingly. Please expect more communication regarding this in the next few days. The next meeting of the OpenStack TC is on 2025-05-27 at 1700 UTC. This meeting will be held over IRC on the #openstack-tc channel on OFTC. 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 ==== - [resolution] Relinquish "quantum" project on PyPI | https://review.opendev.org/c/openstack/governance/+/949783 ==== Open for Review ==== - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - [resolution] Replace CLA with DCO for all contributions | https://review.opendev.org/c/openstack/governance/+/950463 - Clarify actions when no elections are required | https://review.opendev.org/c/openstack/governance/+/949431 - Fix outdated info on the tc-guide | https://review.opendev.org/c/openstack/governance/+/950446 === Upcoming Events === - 2025-06-03: 15 ans d'OpenStack - OpenInfra UG, Paris: https://www.meetup.com/openstack-france/events/307492285 - 2025-06-05: OpenStack 15 ans! - OpenInfra UG, Rennes: https://www.meetup.com/openstack-rennes/events/306903998 - 2025-06-28: OpenInfra+Cloud Native Day, Vietnam: https://www.vietopeninfra.org/void2025 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] "cycle-trailing": https://releases.openstack.org/reference/release_models.html#cycle-trailing [3] "eventlet-removal" status: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [4] TC resolution to replace CLA with DCO for all contributions: https://review.opendev.org/c/openstack/governance/+/950463 [5] OpenStack CLA: https://docs.openstack.org/contributors/common/setup-gerrit.html#individual… [6] Developer Certificate of Origin: https://developercertificate.org/ [7] DCO documentation draft: https://review.opendev.org/c/openstack/contributor-guide/+/950839 [8] TC Meeting IRC Log 2025-05-20: https://meetings.opendev.org/meetings/tc/2025/tc.2025-05-20-17.00.log.html [9] TC Meeting Agenda, 2025-05-27: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

#eventlet-removal - Progress & Updates - Flamingo milestone 1
by Herve Beraud 26 May '25

26 May '25

TL;DR: We just passed the milestone 1 of Flamingo and at this point big fishes like Neutron, Nova, Glance, and Mistral demonstrated awesome progress in their migration. Oslo.service's new backend is now usable in real life use cases. Eventlet still suffers from a new version of Python. If you have not yet started your migration yet, then, please consider starting ASAP before the aircraft crash. ## OpenStack Updates Neutron's L3 agent is well on its way to running its WSGI features without using Eventlet and activating the new oslo.service threading backend at runtime. Allowing to decouple a bit more the needs of Eventlet at runtime. Nova scheduler is now able to start in threading mode without requiring any usage of Eventlet at runtime. This was possible by also shifting nova-scheduler to the threading backend of oslo.service. More details are available here https://gibizer.github.io/categories/eventlet/ Activating the new threading backend of oslo.service required devstack adaptation to allow having jobs running this execution mode. https://review.opendev.org/c/openstack/devstack/+/948436. Everybody will be able to benefit from these adaptations. Glance continues its adaptation journey by migrating its functional jobs to reduce its needs of Eventlet and to allow it to run jobs in threading mode. oslo.service's new backend is on the way to be landed soon, and is waiting for additional reviews. https://review.opendev.org/c/openstack/oslo.service/+/945720 ## Eventlet Updates Our CI was failing for almost 2 months, we were able to unlock this failing CI and hence we were able to merge several blocked reviews. Last week Eventlet 0.40.0 was released. This new version provides fixes around OpenSSL 3.5+. The support of Python 3.8 and of PyPy were removed. The Python 3.13 issues are still not solved and require further work. ## Call to Action Flamingo is a crucial series in the realization of global migration of OpenStack. We need your involvement to accelerate the progress of this initiative! If your project is affected by Eventlet, now is the time to start your migration. Teams are invited to read the migration guide available at https://removal.eventlet.org/ and are encouraged to join the #openstack-eventlet-removal IRC channel to get help. You'll benefit quickly from the advantages of running your deliverables without using Eventlet. ## Final Thoughts Postponing the beginning of the migration will put additional pressure related to growing runtime failures of Eventlet. We want to prevent this from happening to you. We are now going straight to milestone 2 meaning that we will soon be in the middle of Flamingo. The migration path is now well cleared by all the previous actions and changes applied into OpenStack. Do not be afraid by the migration and take advantage of the collected experience. Your journey start here https://removal.eventlet.org/ Thanks for reading. -- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/

4 5

[tc][all] Moving from CLA to DCO for OpenInfra Contributions
by Jonathan Bryce 23 May '25

23 May '25

Hi everyone, I wanted to flag a recent message on the Foundation mailing list about the possibility to move OpenInfra projects from using the Contributor License Agreement (CLA) to the Developer Certificate of Origin (DCO) [1]. This change would be part of the broader transition into the Linux Foundation and could take effect starting June 1, 2025. It’s something the Board has supported for newer projects, and now existing projects like OpenStack have the opportunity to make the switch as well. I’m happy to join the TC meeting this week to discuss. Thanks, Jonathan 1. https://lists.openinfra.org/archives/list/foundation@lists.openinfra.org/th…

8 16

[manila] Manila Bugsquash: Focusing on Reviews
by Carlos Silva 22 May '25

22 May '25

Hello zorillas and interested stackers, Next week, the Manila team will have the first bugsquash of the Flamingo cycle. We have plenty of "In Progress" bugs, so we are planning to focus on reviews for this bugsquash. Vida (vhari) groomed the list for the bugsquash [1]. If there's a change you'd like to have some eyes on over the course of the next week, please add that to the list of changes. We will have a kick-off meeting where we'll get some reviewers to share their tricks while reviewing changes with the whole team. More details to join are available on the ICS [2]. [1] https://etherpad.opendev.org/p/manila-flamingo-m1-bugsquash [2] https://gist.github.com/silvacarloss/5a3d3a548b5a92a5425f88b086855568 Looking forward to it, carloss

1 0

[neutron] Drivers meeting canceled Friday, May 23rd
by Brian Haley 22 May '25

22 May '25

Hello Neutrinos: I'm going to cancel tomorrow's drivers meeting as it does not look like we will have quorum. Please add things to the wiki [0] to discuss next week, we currently have one agenda item planned: * Integrate OVN BGP capabilities into Neutron OVN driver https://bugs.launchpad.net/neutron/+bug/2111276 Have a nice weekend! -Brian [0] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[barbican] Cancel Weekly Meeting
by Mauricio Harley 22 May '25

22 May '25

Hi, guys! We need to cancel the weekly meeting that would happen on Monday the 26th. This is necessary since I'll be on PTO that day. Looking forward to meeting you all on the Monday following: June the 2nd. Best regards, Mauricio

1 0

#eventlet-removal - Announcing the New Threading Backend of oslo.service
by Herve Beraud 22 May '25

22 May '25

I'm happy to announce the new version of oslo.service is out! [1] This new version came out with the new Threading backend [2]. OpenStack Upper constraints are on the way to be upgraded to this new version [3]. You can start using the new threading backend by following the steps below: ``` import oslo_service.backend as service service.init_backend(service.BackendType.THREADING) ``` Ideally this backend selection should be made in your patcher module. Almost all OpenStack services own a household patcher. Neutron and Nova already demonstrated a successful adoption of this new backend on Nova scheduler and Neutron L3 agent: - https://review.opendev.org/c/openstack/neutron/+/938404 - https://review.opendev.org/c/openstack/nova/+/948450/17 Devstack is on the way to be adapted to allow you to set up `SYSTEMD_ENV_VARS`. [4] This will allow passing environment variables from zuul job definitions to systemd service files via the local conf. During the Eventlet removal effort this will allow teams to have separate jobs testing the same service in different concurrency modes. The first use case of this is to implement scenarios like passing variable `OS_NOVA_DISABLE_EVENTLET_PATCHING=true` to nova services that already supports running in native threading mode instead of with Eventlet. To get a more concrete integration example, you can take inspiration from Nova patches [5][6] to see how to implement your backend switch on your deliverables. A comprehensive guide is currently under creation. [7] Next steps will be to address a couple of remaining comments, to introduce functional tests, and to democratize the usages of this new backend. Thank you to Daniel for his hard work and all his efforts on this topic. Also I wanted to specially thank Gibi and Rodolfo for their close collaborations on this new backend implementation. Please join me to warmfully thank them. Our mission is to equip the community with everything it needs to leave Eventlet behind. This backend is only a tiny piece of this giant puzzle. Your turn to place your piece: https://removal.eventlet.org Cheers, [1] https://review.opendev.org/c/openstack/releases/+/950646 [2] https://review.opendev.org/c/openstack/oslo.service/+/945720 [3] https://review.opendev.org/c/openstack/requirements/+/950653 [4] https://review.opendev.org/c/openstack/devstack/+/948436 [5] https://review.opendev.org/c/openstack/nova/+/948311 [6] https://review.opendev.org/c/openstack/nova/+/948450 [7] https://review.opendev.org/c/openstack/oslo.service/+/940664 -- Hervé Beraud Principal Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

"quantum" package name on pypi
by JDK Phoenix 22 May '25

22 May '25

Dear Openstack-Team, I am the creator and maintainer of the programming language "qb" (qb · PyPI <https://pypi.org/project/qb/>, qb <https://lschreiber.eu/qb/>) and I wanted to implement a package manager similar to how Maven, Cargo or Poetry works. I picked the name "quantum" for this program and noticed that this name was already in use on pypi for a package developed by you. This program has only a singular contribution in 2012 and seems to be inactive since then. I wanted to ask if it would be possible for you to transfer the quantum-package name on pypi to my user (Leander420). I would be very grateful if this could be possible. I thank you for your time and consideration Kind regards Leander S. Schreiber

6 6

Issue on IP Assignment on newly created VM after deleting old one
by sudeb ghosh 21 May '25

21 May '25

Hi Team, We are operating an OpenStack environment managed by Ansible. Openstack Version: Ussuri(21.2.1) OS: CentOS8 We had a volume backed VM named VM01 with IP of 10.10.10.10 for example. We required to delete the VM01 & recreate a VM named VM02 using the same volume. We used the same project & same network what we used for VM01 earlier. VM02 is getting any one available IPs from the given network. Manually i am able to detach the existing IP & attached the specific IP but its not pinging. Query: i) What is the option if i need the same IP(10.10.10.10) will be assigned to VM02 as well autometically? ii) What is fix to get the said old IP(10.10.10.10) working if i do attach manually in GUI through newtwork-interface? BR// Sudeb Ghosh 7044064878 9332034788

3 3

[watcher] Call for maintainers - MAAS integration
by Douglas Viroel 20 May '25

20 May '25

Hi everyone, At the last watcher's weekly meeting[1], the team discussed the impacts of the eventlet removal in Watcher's code, and it was brought up that the integration with MAAS (Metal As a Service) support is affected. At the moment, we do not have any active members in Watcher that have any experience with MAAS. CI also doesn't have any job running and testing this integration, and we don't have documentation of how it works. This is a call for maintainers interested in supporting MAAS in Watcher to help fill these gaps. It is worth mentioning that, as discussed in the PTG[2], we also plan to mark this integration as *experimental* once it does not provide minimal testing and documentation (this is also the case of other integrations). But we will cover this topic in a different thread. [1] https://meetings.opendev.org/meetings/watcher/2025/watcher.2025-05-15-12.01… [2] https://etherpad.opendev.org/p/apr2025-ptg-watcher#L71 Thanks and regards, -- Douglas Viroel - dviroel

1 0

[ops][neutron] Neutron-db-manage upgrade from Antelope to Bobcat fails with "foreign key constraint 'porthints_ibfk_1' are incompatible" error
by federica fanzago 20 May '25

20 May '25

Dear all, we are running an OpenStack deployment Yoga on AlmaLinux 9.5 and we are attempting the upgrade Openstack up to Caracal release, one release at time (Zed--Antelope--Bobcat--Caracal) The procedure we are following is to shut down all openstack services, to remove the "old" openstack release and to install the new one, upgrading all service databases. This procedure works well for Zed and Antelope, but during the installation of the Bobcat release, the Neutron database upgrade fails when creating the new "porthints" table. The command we are using is su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head" neutron and the error message we receive is ... File "/usr/lib/python3.9/site-packages/pymysql/err.py", line 107, in raise_mysql_exception raise errorclass(errno, errval) sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (3780, "Referencing column 'port_id' and referenced column 'id' in foreign key constraint 'porthints_ibfk_1' are incompatible.") [SQL: CREATE TABLE porthints ( port_id VARCHAR(36) NOT NULL, hints VARCHAR(4095) NOT NULL, PRIMARY KEY (port_id), FOREIGN KEY(port_id) REFERENCES ports (id) ON DELETE CASCADE )ENGINE=InnoDB ... Our "ports" table uses the collation utf8mb3_general_ci mysql> SHOW FULL COLUMNS FROM ports; +------------------+--------------+--------------------+------+-----+---------+-------+---------------------------------+---------+ | Field | Type | Collation | Null | Key | Default | Extra | Privileges | Comment | +------------------+--------------+--------------------+------+-----+---------+-------+---------------------------------+---------+ | project_id | varchar(255) | utf8mb3_general_ci | YES | MUL | NULL | | select,insert,update,references | | | id | varchar(36) | utf8mb3_general_ci | NO | PRI | NULL | | select,insert,update,references | | | name | varchar(255) | utf8mb3_general_ci | YES | | NULL | | select,insert,update,references | | | network_id | varchar(36) | utf8mb3_general_ci | NO | MUL | NULL | | select,insert,update,references | | | mac_address | varchar(32) | utf8mb3_general_ci | NO | | NULL | | select,insert,update,references | | | admin_state_up | tinyint(1) | NULL | NO | | NULL | | select,insert,update,references | | | status | varchar(16) | utf8mb3_general_ci | NO | | NULL | | select,insert,update,references | | | device_id | varchar(255) | utf8mb3_general_ci | NO | MUL | NULL | | select,insert,update,references | | | device_owner | varchar(255) | utf8mb3_general_ci | NO | | NULL | | select,insert,update,references | | | standard_attr_id | bigint | NULL | NO | UNI | NULL | | select,insert,update,references | | | ip_allocation | varchar(16) | utf8mb3_general_ci | YES | | NULL | | select,insert,update,references | | +------------------+--------------+--------------------+------+-----+---------+-------+---------------------------------+---------+ in Bobcat the collation required for the new "porthints" table is latin1_swedish_ci MariaDB [neutron]> show create table porthints; +-----------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Table | Create Table | +-----------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | porthints | CREATE TABLE `porthints` ( `port_id` varchar(36) NOT NULL, `hints` varchar(4095) NOT NULL, PRIMARY KEY (`port_id`), CONSTRAINT `porthints_ibfk_1` FOREIGN KEY (`port_id`) REFERENCES `ports` (`id`) ON DELETE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_swedish_ci | So, we have tried to create the porthints table in mysql, forcing the collation to utf8mb3_general_ci mysql> CREATE TABLE porthints ( port_id VARCHAR(36) NOT NULL, hints VARCHAR(4095) NOT NULL, PRIMARY KEY (port_id), FOREIGN KEY(port_id) REFERENCES ports (id) ON DELETE CASCADE )ENGINE=InnoDB DEFAULT CHARSET=utf8 DEFAULT COLLATE utf8mb3_general_ci; and commenting out the creation of the new table in the neutron code /usr/lib/python3.9/site-packages/neutron/db/migration/alembic_migrations/versions/2023.2/expand/6f1145bff34c_port_hints.py. In this way, the upgrade works, but we encounter the same kind of problem during the upgrade to Caracal, specifically with the creation of the new table porthardwareoffloadtype. Have you already encountered this issue during the Neutron upgrade? Do you have any suggestions on how to upgrade the neutron DB, without manually creating new tables? Thanks a lot, cheers, Federica -- Federica Fanzago INFN Sezione di Padova Via Marzolo, 8 35131 Padova - Italy Tel: +39 049.967.7367 --

4 8

Osprofiler and nova
by engineer2024 20 May '25

20 May '25

Team, I am facing an issue with osprofiler in nova, where the 'trace show' is failing. I have filed a bug at https://bugs.launchpad.net/osprofiler/+bug/2111345 But I don't see any recent activity there. Is the osprofiler project active ? Please guide me as per the issue mentioned there... Thanks elinux

1 0

[publiccloud-sig] Next meeting of Public Cloud SIG - May 21st at 0700 UTC
by Felix Kronlage-Dammers 20 May '25

20 May '25

Hi everyone, This upcoming Wednesday (May 21st - this is tomorrow :) 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 See you tomorrow! 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

CEPH deployment method: cephadm vs puppet
by Francesco Di Nucci 20 May '25

20 May '25

Hi all, we're planning (finally) to setup a CEPH cluster to be used as OpenStack backend. The cloud is actually set up with Foreman+Puppet, to setup CEPH what would you advice? cephadm as it's the preferred method in the CEPH docs or Puppet with the puppet-ceph module, as it's part of openstack? Thanks in advance -- Francesco Di Nucci System Administrator Compute & Networking Service, INFN Naples Email: francesco.dinucci(a)na.infn.it

6 14

[Patch Management] [Openstack-2024.1 (caracal)]
by Shalini Srivastava 20 May '25

20 May '25

Hello Sir/Ma'am, I need to implement Security update that is Patch management, Vulnerability Management to my Openstack environment that is 2024.1 (Caracal release). The services needs to upgrade as well as update according to the upper constraints available for the given release. Please guide me the steps/procedure for the same. Hope to hear from you soon. Thanks & Regards, Shalini Srivastava Project Associate /प्रोजेक्ट एसोसिएट Centre for Development of Advanced Computing(C-DAC) / प्रगत संगणन विकास केन्द्र(सी-डैक) Tidel Park”, 8th Floor, “D” Block, (North &South) / “टाइडल पार्क”,8वीं मंजिल, “डी” ब्लॉक, (उत्तर और दक्षिण) No.4, Rajiv Gandhi Salai / नं.4, राजीव गांधी सलाई Taramani / तारामणि Chennai / चेन्नई – 600113 Ph.No.:044-22542226/27 Fax No.: 044-22542294 ------------------------------------------------------------------------------------------------------------ [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------

1 0

Guidance related to [Patch Management] [Openstack-2024.1 (caracal)]
by Shalini Srivastava 20 May '25

20 May '25

Hello Sir/Ma'am, I need to implement a Security update that is Patch management, Vulnerability Management to my Openstack environment that is 2024.1 (Caracal release). The services need to upgrade as well as update according to the upper constraints available for the given release. Please guide me the steps/procedure for the same. Hope to hear from you soon. Thanks & Regards, *Shalini Srivastava* Project Associate /प्रोजेक्ट एसोसिएट Centre for Development of Advanced Computing(C-DAC) / प्रगत संगणन विकास केन्द्र(सी-डैक) Tidel Park”, 8th Floor, “D” Block, (North &South) / “टाइडल पार्क”,8वीं मंजिल, “डी” ब्लॉक, (उत्तर और दक्षिण) No.4, Rajiv Gandhi Salai / नं.4, राजीव गांधी सलाई Taramani / तारामणि Chennai / चेन्नई – 600113 Ph.No.:044-22542226/27 Fax No.: 044-22542294

1 0

[magnum] April vPTG summary and Magnum meeting time change
by Dale Smith 20 May '25

20 May '25

Hello all, I wanted to post a short summary to this list of the vPTG[1] the Magnum team held on April 8th and 9th 2025. These are the topics and a summary of my notes from the discussions. If I missed key details please add these to the etherpad and/or reply here. Thank you all for attending. Please get in touch if the timing of the vPTG did not work for you, as we could propose multiple timezone slots in future. * Heat driver deprecation. o This driver is marked deprecated in Dalmation 2025.1, being replaced by either of the Cluster API drivers, and we discussed when and how we will remove it from Magnum codebase. o We are now looking at removing the Heat driver in this (Flamingo 2025.2) cycle, as waiting longer may imply waiting until 2026.2 due to SLURP release expectations. We would like to hear any feedback on this plan from users of Magnum - either in the mailing list or join one of our IRC meetings[2]. o One option is to move the driver out of tree into its own codebase (perhaps in `x/`), to allow deployers to keep their existing clusters functional and addressable by Magnum while transitioning to a Cluster API driver. This initiative needs effort and a champion to drive it. * Helm charts (magnum-capi-helm driver) o While the driver code is now in opendev the Helm charts live in azimuth-cloud's github. These are a major component of the driver and we discussed the reasoning behind keeping them in github and stability of the Magnum-capi-helm driver. o The current proposal is to snapshot the upstream repo at regular intervals into the opendev repo. This avoids maintenance of a complete fork, but keeps the Magnum-capi-helm driver with a stable internal reference of the helm charts. * CI for the Magnum project was discussed o One big implication of the Heat driver being removed is what we test against. o Including the CAPI drivers (initially non-voting) would give stability, provided external changes wouldn't break the CI. * Normalised labels proposal o Dale has a proposal for Normalised labels[3], aiming for Mutable labels. The video format discussion of the vPTG was very helpful to give context and move the idea forward to cover API backwards compatibility requirements and a better way to implement support labels for different drivers. o The proposal as it stands should be re-worked to look at covering a similar extension pattern that Nova has with drivers, and possibly look to replace labels. * TC initiatives o We discussed the upcoming Eventlet removal and as we are a small team we will wait for guidance and examples to follow before implementing, but we remain aware of this initiative. Finally, I wanted to announce to the list that at last weeks Magnum IRC meeting we proposed and agreed on a new time slot. This is on alternate (every second) Tuesday at 8am UTC starting on the 27th May[2]. See the meeting notes for a full transcript and discussion[4]. Links and references: [1] Magnum vPTG topics and notes can be found on https://etherpad.opendev.org/p/apr2025-ptg-magnum [2] Magnum weekly meeting times and agenda, https://etherpad.openstack.org/p/magnum-weekly-meeting [3] Normalisation of labels proposal, https://review.opendev.org/c/openstack/magnum-specs/+/943358 [4] Magnum meeting 2025-05-14, https://meetings.opendev.org/meetings/magnum/2025/magnum.2025-05-14-09.00.l… Thank you for reading! (or skim reading!) Dale Smith Magnum PTL for Epoxy cycle.

1 0

[adjutant] Adding Callum Dickinson to core group
by Dale Smith 20 May '25

20 May '25

Hello all, The project Adjutant is adding Callum Dickinson to the core group. Callum has contributed features, bugfixes and reviews code in the Adjutant project. I want to note that both of us are from the same company, Catalyst Cloud, and keeping the project alive by using it internally. We will always welcome other contributors, and don't want to keep this project exclusive. regards, Dale, Adjutant PTL -- DALE SMITH Cloud Engineer Catalyst Cloud <https://catalystcloud.nz> Aotearoa New Zealand's cloud provider e dale(a)catalystcloud.nz w catalystcloud.nz <https://catalystcloud.nz> Follow us on LinkedIn <https://www.linkedin.com/company/catalyst-cloud-limited/> Level 6, Catalyst House, 150 Willis St, Wellington 6011 Confidentiality Notice: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267 <tel:+6444992267>.

1 0

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

20 May '25

Hello Stackers, We are 19 weeks away from the release date for OpenStack 2025.2 "Flamingo" [1]. Last week, election officials published the combined TC and PTL election schedule targeting the next release cycle [2]. We are setting up our election configuration early to ensure that community members have adequate time to propose and deliberate nominations. The elections themselves will occur in August 2025, and the official nominations window opens on 2025-08-06 (week R-8). However, you are welcome to submit your candidacy early in case you anticipate being away. Please note that your nomination will not be merged until the nomination window opens. This election is also an opportunity for OpenStack project teams to modify their leadership model if they choose. All project teams with "distributed" project leadership will be required to update their liaisons or assert that no change is necessary by week R-8. Please await changes from the TC on Gerrit to do so. No further governance changes were made last week; however, a few proposals are open for review. === Weekly Meeting === The weekly IRC meeting of the OpenStack Technical Committee occurred on 2025-05-13 [3]. A lot of progress was made in the past few weeks with regard to action items that we were tracking from our Project Team Gathering in April. We discussed a proposal [4] to require a declaration of affiliation when contesting TC elections and how that would apply to current TC members. The proposal seeks to enhance transparency and allow voters to make more informed choices since the TC has an affiliation diversity requirement [5] that is enforced when adopting the results of an election. Concerns were raised about potential misinterpretations regarding company influence and the perception of OpenStack's governance. It was recommended that we add specific disclaimers as to why the affiliation is declared on our governance pages after this proposal has been adopted. We also socialized the kick-off for the 2026.1 elections. I will be serving as the TC's election liaison and helping our election officials Slawek Kaplonski (slaweq) and Ian Y Choi (ianychoi). We discussed the state of the CI, bringing the TC up to speed on several cross-community CI efforts. The next meeting of the OpenStack TC is on 2025-05-20 at 1700 UTC. This meeting will be held over IRC on the #openstack-tc channel on OFTC. Please find the agenda and other details in the meeting's wiki page [6]. I hope you will be able to join us there! === Governance Proposals === === Open for review === - [resolution] Relinquish "quantum" project on PyPI | https://review.opendev.org/c/openstack/governance/+/949783 - Require declaration of affiliation from TC Candidates | https://review.opendev.org/c/openstack/governance/+/949432 - Clarify actions when no elections are required | https://review.opendev.org/c/openstack/governance/+/949431 === Upcoming Events === - 2025-05-22: OpenInfra UG Meetup, Sweden: https://www.meetup.com/openinfra-user-group-sweden/events/306139678/ - 2025-06-03: 15 ans d'OpenStack - OpenInfra UG, Paris: https://www.meetup.com/openstack-france/events/307492285 - 2025-06-05: OpenStack 15 ans! - OpenInfra UG, Rennes: https://www.meetup.com/openstack-rennes/events/306903998 - 2025-06-28: OpenInfra+Cloud Native Day, Vietnam: https://www.vietopeninfra.org/void2025 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 TC+PTL Elections: https://governance.openstack.org/election/ [3] TC Meeting IRC Log 2025-05-13: https://meetings.opendev.org/meetings/tc/2025/tc.2025-05-13-17.00.html [4] Require declaration of affiliation from TC Candidates: https://review.opendev.org/c/openstack/governance/+/949432 [5] OpenStack TC's affiliation diversity requirement: https://governance.openstack.org/tc/reference/charter.html#tc-diversity-req… [6] TC Meeting Agenda, 2025-05-20: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[ironic] No meeting May 26, 2025
by Jay Faulkner 19 May '25

19 May '25

Hi all, We're cancelling the meeting for next Monday, May 26, due to it overlapping with the US Memorial Day holiday. Thanks, Jay Faulkner Ironic Security Liason

1 0

Guidance related to Patch Management in Openstack-2024.1 (caracal)
by Shalini Srivastava 19 May '25

19 May '25

Hello Sir, I need to implement Security update that is Patch management, Vulnerability Management to my Openstack environment that is 2024.1 (Caracal release). The services needs to upgrade as well as update according to the upper constraints available for the given release. Please guide me the steps/procedure for the same. Hope to hear from you soon. Thanks & Regards, Shalini Srivastava Project Associate /प्रोजेक्ट एसोसिएट Centre for Development of Advanced Computing(C-DAC) / प्रगत संगणन विकास केन्द्र(सी-डैक) Tidel Park”, 8th Floor, “D” Block, (North &South) / “टाइडल पार्क”,8वीं मंजिल, “डी” ब्लॉक, (उत्तर और दक्षिण) No.4, Rajiv Gandhi Salai / नं.4, राजीव गांधी सलाई Taramani / तारामणि Chennai / चेन्नई – 600113 Ph.No.:044-22542226/27 Fax No.: 044-22542294 ------------------------------------------------------------------------------------------------------------ [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------

1 0

[neutron] Bug deputy report (week starting on May 12)
by Bernard Cafarelli 19 May '25

19 May '25

Hey neutrinos, here is the list of bugs reported last week Overall a quiet week, bugs are assigned with proposed (or merged already) patch, except a CI failure report (no immediate action needed, mostly for tracking if the failure reappears) High * Neutron endpoint options are not applied - https://bugs.launchpad.net/neutron/+bug/2110488 ovn-octavia-provider similar to a fixed Octavia issue, proposed updated patch by priteau: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/925893 * "neutron-tempest-plugin-designate-scenario-zed" job failing - https://bugs.launchpad.net/neutron/+bug/2110550 Needed to pin the tempest plugin to zed-last, fix by ralonsoh merged: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/949643 Medium * occasional functional test failure: neutron.tests.functional.privileged.agent.linux.test_utils.FindListenPidsNamespaceTestCase.test_find_listen_pids_namespace - https://bugs.launchpad.net/neutron/+bug/2110878 CI failure but seen once in gate for now * ovs-agent: Leftover tpi/spi interfaces after VM boot/delete with trunk port(s) - https://bugs.launchpad.net/neutron/+bug/2095152 Trunk ports leftover for ML2/OVS following a change for ML2/OVN, see bug for details (reproducer) Patch proposed by rubasov: https://review.opendev.org/c/openstack/neutron/+/949217 -- Bernard Cafarelli

1 0