- openstack-discuss - lists.openstack.org

[openstack-helm][loci] Retire Centos based images
by Vladimir Kozhukalov 28 May '25

28 May '25

Hi team, We have a bunch of Centos related stuff in the Loci repo. However we've not been building and testing centos based images for quite some time. Is anybody still interested in having/maintaining this stuff? I am talking about [1] - [5]. [1] https://opendev.org/openstack/loci/src/branch/master/dockerfiles/centos [2] https://opendev.org/openstack/loci/src/branch/master/scripts/install.sh#L37… [3] https://opendev.org/openstack/loci/src/branch/master/scripts/collect_info.s… [4] https://opendev.org/openstack/loci/src/branch/master/scripts/install_packag… [5] https://opendev.org/openstack/loci/src/branch/master/scripts/cleanup.sh#L14… -- Best regards, Kozhukalov Vladimir

1 1

Re: [neutron] Switching the ML2 driver in-place from linuxbridge to OVN for an existing Cloud
by Ohnsorge Borys 28 May '25

28 May '25

Hi James, I know this topic is old, but have you had the time/opportunity to describe the migration process based on openstack-ansible You mentioned? __ Best regards Borys Ohnsorge

2 1

[largescale-sig] Next meeting: May 28, 15utc
by Thierry Carrez 28 May '25

28 May '25

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC at 15UTC. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250528T15 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[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