March 2025 - openstack-discuss - lists.openstack.org

Nova features
by engineer2024 26 Mar '25

26 Mar '25

Where can I find the nova feature requests which are yet to be developed ? I am thinking of contributing to adding new features.

3 3

[largescale-sig] Next meeting: March 26, 16utc
by Thierry Carrez 26 Mar '25

26 Mar '25

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 16UTC to facilitate America timezones participation. In these troubled DST times, you should doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250326T16 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

2 1

#eventlet-removal Flamingo PTG
by Herve Beraud 26 Mar '25

26 Mar '25

Hello folks, We’re meeting again on the Project Teams Gathering in April (7-11th). The slot for the Eventlet Removal Initiative PTG is: Tuesday (Apr 8) 1400-1600 UTC The etherpad is: https://etherpad.opendev.org/p/apr2025-ptg-eventlet Please feel free to insert your topic proposals. Additional details can be found at https://ptg.opendev.org/ Regards, -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[release][ptl][tc] OpenInfra Live for OpenStack 2025.1 ‘Epoxy’
by helena＠openinfra.dev 26 Mar '25

26 Mar '25

Hi everyone, Following the release of OpenStack 2025.1 ‘Epoxy’ next Wednesday, we'd like to go ahead and schedule the OpenInfra Live for Thursday, April 3 at 1400 UTC. If you would like to represent your project team’s updates in the Epoxy release as well as their plans for Flamingo, please let me know. If you are not familiar, you can find reference examples like 2024.2 Dalmation [1] and 2024.1 Caracal [2]. [1] https://www.youtube.com/watch?v=6igJNIJ9yFE [2] https://www.youtube.com/watch?v=3BgAXbFaVqw&t=1707s Thanks! Helena helena(a)openinfra.dev Community Programs Manager The OpenInfra Foundation [openinfraLogo-sm.png]

3 2

[neutron][ops][upgrade] l3-agent failure during upgrade to Zed
by Eugen Block 25 Mar '25

25 Mar '25

Hi *, maybe I missed some announcement or something, but usually, I read the release notes [0] before upgrading our OpenStack cloud. I didn't notice anything regarding DB schema upgrades. And after the upgrade from Yoga to Zed in a test environment went well, I tried the same in our production today. Note that I didn't have a router in my test cloud, so that's probably why I didn't notice anything. Unfortunately, there has been a schema change, that's why the l3-agent failed to start properly with this error: 2025-03-21 12:29:14.527 846393 CRITICAL neutron [None req-e225ff0a-82e1-473b-9eba-9a11caa7ace7 - - - - - -] Unhandled error: oslo_messaging.rpc.client.RemoteError: Remote error: OperationalError (pymysql.err.OperationalError) (1054, "Unknown column 'portforwardings.external_port' in 'SELECT'") Indeed, the upgraded control node didn't have "external_port" anymore in /usr/lib/python3/dist-packages/neutron/db/models/port_forwarding.py, while the not yet upgraded control node did. So the situation could only be resolved by proceeding with the upgrade. But that meant an interruption for our virtual routers, causing floating IPs to be unreachable for a couple of minutes. Note that we're using highly-available routers. I thought about setting "no-ha" for each router, but that can only be done for disabled routers, which is not an option, of course. And it doesn't really fit into the "rolling upgrade" concept, which has worked great so far. Since we moved to Ubuntu last September (while still on Victoria), we've been able to upgrade to Yoga without any issues. And while the interruption today was not too critical, I was still surprised that such an important change didn't even make it into the Zed release notes. Was that a mistake or did I miss something? Are there other places I need to check before attempting an upgrade? Thanks, Eugen [0] https://docs.openstack.org/releasenotes/neutron/zed.html

3 9

[dev] New contributing organization help
by Dominik Danelski 25 Mar '25

25 Mar '25

Hello community, I work at a silver member of OpenInfra and will make code contributions on behalf of my employer. I am aware about the requirement to sign Contributor License Agreement listing me as the responsible person. Other than that, are there any additional requirements on identifying me as a corporate developer? For example contributor guide lists creating INDIVIDUAL Member account as one of the setup steps and it got me a bit worried. Kind regards Dominik Danelski @ CloudFerro

4 3

[kolla] Flamingo PTG
by Michał Nasiadka 25 Mar '25

25 Mar '25

Hello Koalas, We’re meeting again on the Project Teams Gathering in April (7-11th). The slots for Kolla/Kolla-Ansible/Kayobe PTG are: Tuesday - 07:00-08:00 UTC (general, Kolla and Kolla-Ansible) Wednesday - 07:00-08:00 UTC (general, Kolla and Kolla-Ansible) Friday - 14:00-15:00 UTC (Kayobe) If there’s a need of an additional afternoon (UTC) slot - please let us know. The ether pad is at the usual location: https://etherpad.opendev.org/p/kolla-flamingo-ptg Please insert your topic proposals and see you on the PTG. Additional details can be found at https://ptg.opendev.org/ Cheers, Michal

1 0

[publiccloud-sig] Next meeting of Public Cloud SIG upcoming - March 26th at 0800 UTC
by Felix Kronlage-Dammers 25 Mar '25

25 Mar '25

Hi everyone, This upcoming Wednesday (March 26th) the next meeting of the publiccloud-sig is going to happen. We’ll be meeting at 0800 UTC here: https://meetpad.opendev.org/publiccloud-sig See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG I'll not be around but Artem (gtema) will be hosting the call. Thanks Artem! 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

[openstack][rabbitmq]computes cannot register to nova 2025.0master
by Nguyễn Hữu Khôi 25 Mar '25

25 Mar '25

Hello. I deployed OpenStack 2025.1 Master with Kolla-Ansible, but the compute nodes cannot register with Nova. Error: Cannot update service status on host "compute05" due to an unexpected exception.: oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 3dad7dbe8ea9429c83958b98bccc7094 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver Traceback (most recent call last): 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/virt/libvirt/driver.py", line 5687, in _set_host_enabled 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver service = objects.Service.get_by_compute_host(ctx, CONF.host) 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/oslo_versionedobjects/base.py", line 175, in wrapper 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver result = cls.indirection_api.object_class_action_versions( 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/nova/conductor/rpcapi.py", line 240, in object_class_action_versions 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver return cctxt.call(context, 'object_class_action_versions', 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/oslo_messaging/rpc/client.py", line 190, in call 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver result = self.transport._send( 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/oslo_messaging/transport.py", line 123, in _send 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver return self._driver.send(target, ctxt, message, 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 800, in send 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver return self._send(target, ctxt, message, wait_for_reply, timeout, 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 789, in _send 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver result = self._waiter.wait(msg_id, timeout, 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 654, in wait 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver message = self.waiters.get(msg_id, timeout=timeout) 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver File "/var/lib/kolla/venv/lib/python3.12/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 520, in get 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver raise oslo_messaging.MessagingTimeout( 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 3dad7dbe8ea9429c83958b98bccc7094 2025-03-23 10:31:26.974 7 ERROR nova.virt.libvirt.driver All services are in a "down" state, but this issue only occurs when using a three-controller cluster. When I use a single controller, everything works fine. My Env: OS: Ubuntu 22.04 OpenStack Version: 2025.1 Master Deployment Tool: Kolla-Ansible 19 Thank you. Nguyen Huu Khoi

3 7

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-1)
by Goutham Pacha Ravi 25 Mar '25

25 Mar '25

Hello Stackers, We're one week away from the coordinated release of OpenStack 2025.1 ("Epoxy") [1]. Project teams shipped release candidates over the past week and will keep these updated if any release-critical bugs are identified. Teams are also preparing for the virtual OpenInfra Project Teams Gathering (PTG) [2], which begins on April 7. OpenStack project teams are encouraged to schedule cross-project meetings during the first two days. The OpenStack Technical Committee will meet with contributors to chart out our tasks to aid the next release, 2025.2 "Flamingo." The TC sessions are scheduled at the beginning and end of the PTG. We hope to discuss governance, community goals, and other work affecting the entire community. Please find the etherpad of the OpenStack TC's discussions [3], and feel free to propose new topics! In the past week, the TC appointed its chair (me!) and vice-chair (Dmitriy Rabotyagov / noonedeadpunk). We thank the members of the TC and the community for their continued faith in our work. Additionally, a proposal has been made to change the Vulnerability Management Team's (VMT) work, which will affect all project teams [4]. The proposal aims to place all project teams under VMT's oversight. Your feedback on this proposal is welcome! === Weekly Meeting === The OpenStack TC met on OFTC's #openstack-tc channel for its weekly meeting on 2025-03-18 [5]. We began with a discussion around the former openstack-operators mailing list. This mailing list was merged with the openstack-discuss mailing list after extensive prior discussion. The TC received some feedback in recent months from operators who wished to revive a dedicated list for operator discussions. Some operators feel project maintainers don’t engage with their problems, and discussions now occur on other platforms. Mailing list engagement among operators is still present but could be improved. There will be an Operators Discussion at the PTG, and the TC will raise this concern to better understand operator feedback. The TC appreciated the work project teams did in conjunction with the release team to get release candidates posted across the board. We reviewed the state of the CI and welcomed the donation of cloud resources that aided in Zuul's scalability around this critical time of the release. The next meeting of the OpenStack Technical Committee is today, 2025-03-25. It will be held at 18:00 UTC in the #openstack-tc channel on OFTC. Please find the agenda on the meeting's wiki page [6]. I hope you'll be able to join us. === Governance Proposals === ==== Merged ==== - Add 2025.2 TC chair and vice-chair | https://review.opendev.org/c/openstack/governance/+/944174 - Add separate freezer-api deliverable | https://review.opendev.org/c/openstack/governance/+/944781 ==== Open for Review ==== - [resolution] Extend scope of VMT to cover all project teams | https://review.opendev.org/c/openstack/governance/+/944817 - Add Cinder Huawei charm | https://review.opendev.org/c/openstack/governance/+/867588 === Upcoming Events === - 2025-04-01 - 2025-04-04: KubeCon+CloudNativeCon EU: https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/ - 2025-04-02: OpenStack 2025.1 ("Epoxy") Release - 2025-04-03: OpenInfra LIVE - Epoxy release - 2025-04-08: OpenInfra Board Meeting: https://board.openinfra.org/ - 2025-04-07 - 2025-04-12: OpenInfra PTG Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] 2025.2 "Flamingo" PTG: https://openinfra.org/ptg/ [3] TC PTG Etherpad: https://etherpad.opendev.org/p/apr2025-ptg-os-tc [4] VMT proposal: https://review.opendev.org/c/openstack/governance/+/944817 [5] TC Meeting IRC Log 2025-03-18: https://meetings.opendev.org/meetings/tc/2025/tc.2025-03-18-18.00.log.html [6] TC Meeting Agenda, 2025-03-25: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0