- openstack-discuss - lists.openstack.org

[nova][ci] nova-live-migration-ceph job failing 100%
by melanie witt 18 Feb '26

18 Feb '26

We have another gate blockage going on right now with the nova-live-migration-ceph job which began to fail sometime on 2026-02-12 on the master branch: https://zuul.opendev.org/t/openstack/builds?job_name=nova-live-migration-ce… failing in the post stage with errors: 2026-02-17 15:33:11.163476 | LOOP [run-evacuate-hook : Stop libvirtd on "controller"] 2026-02-17 15:33:14.016935 | controller | changed: "libvirtd.service" 2026-02-17 15:33:14.671190 | controller | changed: "libvirtd.socket" 2026-02-17 15:33:15.286503 | controller | ok: "libvirtd-admin.socket" 2026-02-17 15:33:15.922638 | controller | ok: "libvirtd-ro.socket" 2026-02-17 15:33:19.293538 | controller | changed: "virtlogd.service" 2026-02-17 15:33:19.918949 | controller | changed: "virtlogd-admin.socket" 2026-02-17 15:33:20.541634 | controller | changed: "virtlogd.socket" 2026-02-17 15:33:21.114233 | controller | ERROR: Item: virtlockd.service 2026-02-17 15:33:21.114481 | controller | { 2026-02-17 15:33:21.114549 | controller | "ansible_loop_var": "item", 2026-02-17 15:33:21.114602 | controller | "item": "virtlockd.service", 2026-02-17 15:33:21.114652 | controller | "msg": "Could not find the requested service virtlockd.service: host" 2026-02-17 15:33:21.114702 | controller | } 2026-02-17 15:33:21.673927 | controller | ERROR: Item: virtlockd-admin.socket 2026-02-17 15:33:21.674126 | controller | { 2026-02-17 15:33:21.674189 | controller | "ansible_loop_var": "item", 2026-02-17 15:33:21.674242 | controller | "item": "virtlockd-admin.socket", 2026-02-17 15:33:21.674332 | controller | "msg": "Could not find the requested service virtlockd-admin.socket: host" 2026-02-17 15:33:21.674388 | controller | } 2026-02-17 15:33:22.221836 | controller | ERROR: Item: virtlockd.socket 2026-02-17 15:33:22.222026 | controller | { 2026-02-17 15:33:22.222090 | controller | "ansible_loop_var": "item", 2026-02-17 15:33:22.222188 | controller | "item": "virtlockd.socket", 2026-02-17 15:33:22.222259 | controller | "msg": "Could not find the requested service virtlockd.socket: host" 2026-02-17 15:33:22.222363 | controller | } This might be related to a recent change in openstack/devstack-plugin-ceph that merged on Feb 12: https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/976279 The breakage is being worked on in the following proposed patches: https://review.opendev.org/q/topic:%22nova-livemigration-ceph%22 Please hold your rechecks if your patch has failed CI due to this issue. -melwitt

1 1

[OSSA-2026-002] OpenStack Nova: calls qemu-img without format restrictions for resize (CVE-2026-24708)
by Jeremy Stanley 17 Feb '26

17 Feb '26

========================================================================= OSSA-2026-002: Nova calls qemu-img without format restrictions for resize ========================================================================= :Date: January 17, 2026 :CVE: CVE-2026-24709 Affects ~~~~~~~ - Nova: <30.2.2, >=31.0.0 <31.2.1, >=32.0.0 <32.1.1 Description ~~~~~~~~~~~ Dan Smith from Red Hat reported a vulnerability in nova. By writing a malicious QCOW header to a root or ephemeral disk and then triggering a resize, a user may convince Nova's flat image backend to call qemu-img without a format restriction resulting in an unsafe image resize operation that could destroy data on the host system. Only compute nodes using the Flat image backend (usually configured with use_cow_images=False) are affected. Patches ~~~~~~~ - https://review.opendev.org/977104 (2024.2/dalmatian) - https://review.opendev.org/977103 (2025.1/epoxy) - https://review.opendev.org/977101 (2025.2/flamingo) - https://review.opendev.org/977100 (2026.1/gazpacho) Credits ~~~~~~~ - Dan Smith from Red Hat (CVE-2026-24708) References ~~~~~~~~~~ - https://launchpad.net/bugs/2137507 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-24709 -- Jeremy Stanley OpenStack Vulnerability Management Team https://security.openstack.org/vmt.html

1 2

[election][cloudkitty] PTL candidacy for the 2026.2 release cycle
by Rafael Weingärtner 17 Feb '26

17 Feb '26

Hi all, I would like to self-nominate for the role of PTL of CloudKitty for the 2026.2 release cycle. I have been PTL since the Victoria cycle and I am willing to continue in this role. I will keep working with existing contributors to maintain CloudKitty for their use cases and encourage the addition of new functionalities. I have opened the patch with my candidacy: https://review.opendev.org/c/openstack/election/+/977071 -- Rafael Weingärtner

1 0

Fw: Zuul8.0 is not posting logs url into Opendev review commit
by Vasudevan, Senthil 17 Feb '26

17 Feb '26

Hello Team, We recently upgraded our CI environment from Zuul 3 to Zuul 8. Post that Opendev stopped depicting cutom github url that is log_url: We come to know that Zuul 8 onwards the account used for the integration of opendev gerrit and local zuul should have reviewer access to post comment back into commits. Would you please suggest any workaround or solution available to overcome it. Regards, Senthil V ________________________________ From: Vasudevan, Senthil Sent: Friday, February 6, 2026 5:31 PM To: zuul-discuss(a)lists.zuul-ci.org <zuul-discuss(a)lists.zuul-ci.org> Subject: Zuul8.0 is not posting logs url into Opendev review commit Hello Team, We have Zuul CI servers for HPE Cinder and Manilia drivers. We had Zuul 3.0 version earlier that posted external logs URL successfully back into Opendev gerrit. Once we upgraded the Zuul to 8.0 version, the URL is not posted to Opendev review commits. Looks the account used for Zuul and Opendev integration(http credentials are used for the integration) needs reviewer permission for Zuul version 8 and above. So please let me know whether that is mandatory to have reviewer access and if there are any workaround to post the URL to Opendev gerrit. Thanks, Senthil V

1 0

[Neutron] Bug Deputy Report Feb 9 - Feb 16
by Miro Tomaska 16 Feb '26

16 Feb '26

Hello Neutron, Here is the list of bugs from February 9th until the 16th. *High:* https://bugs.launchpad.net/neutron/+bug/2141546 - Neutron cleans OVN static routes it does not own Assigned: Martin Morgenstern *Medium:* https://bugs.launchpad.net/neutron/+bug/2141648 - [OVN] Allowed address pair with VMAC is not working in ML2/OVN Assigned: Rodolfo Alonso https://bugs.launchpad.net/neutron/+bug/2141908 - Optimize ``neutron.common.ovn.acl.update_acls_for_security_group`` Assigned: Rodolfo Alonso *Undecided: * https://bugs.launchpad.net/neutron/+bug/2141745 - Port in admin down does not send vif plugged events to nova Edit Unassigned *RFE:* https://bugs.launchpad.net/neutron/+bug/2141626 - [RFE] Remote-managed PF Plugging in OVN Driver Assigned: Dmitrii Shcherbakov *Waiting for more data:* https://bugs.launchpad.net/neutron/+bug/2141526 https://bugs.launchpad.net/neutron/+bug/2141530 It would be great to see full logs, but the OP is also using a Rocky release which is EOL. I will ask if this is also an issue on maintenance releases. https://bugs.launchpad.net/neutron/+bug/2141784 - Trunk: not able to filter trunks by their status It seems to work for me on master, waiting for more information -- Miro Tomaska

1 0

[kolla-ansible] Migration from OVS to OVN
by Winicius Allan 16 Feb '26

16 Feb '26

Hi kolla o/ I was searching to see if Kolla currently supports migration from OVS to OVN, and I've found this email thread [1]. I'd like to know if this feature has been implemented, and if so, what the necessary steps are. [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032785.h… Best regards

3 3

April 2026 PTG Team Signup Kickoff
by Kendall Nelson 16 Feb '26

16 Feb '26

Hello Everyone! The next OpenInfra PTG[1] will take place April 20-24, 2026 and registration for the event is now open[2]! For those new to the community, or perhaps just need the reminder, the PTG is a semi-annual event where project teams come together to hash out important details for the next six-ish months during a concentrated set of meetings that often include code sprints, bug fixing, design discussion, and cross project collaboration. To sign your team up, you must complete the survey[3] by March 1st at 7:00 UTC. If your team is not interested in participating, there is no need to fill out the survey. The contact information (email and preferably also IRC nickname) in the form will be used to share important details with moderators about team signup and further logistics. To ensure you receive all communications please double check and submit *ACCURATE* information! If you are not on IRC, please get on the OFTC network[4] and join #openinfra-events as much of the coordination for the event will be done in the #openinfra-events channel. You are also encouraged to familiarize yourself with the PTGBot documentation[5] as well. If you have any questions, please reach out to ptg(a)openinfra.org! Information about signing up for time slots will be sent to moderators shortly after the team signup deadline. -Kendall (diablo_rojo) [1] PTG Site: https://openinfra.org/ptg/ [2] PTG Registration: https://ptg.openinfra.org/ [3] Team Survey: https://openinfrafoundation.formstack.com/forms/apr2026_ptg_survey [4] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [5] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst

1 1

February 4 Meeting Recap & Next Steps
by Kendall Nelson 16 Feb '26

16 Feb '26

Hello folks! Thank you for all your participation thus far - watching the previous recording, answering the last poll, attending the meetings, etc. Here is the recording from today's meeting for those that were unable to attend it live: https://zoom.us/rec/share/9vo8njF87mFdFQhsYdZzYBrY3DSfeuo5t2EJIxMdV4CCtslQs… If you do watch, I would encourage you to add your name and details to the etherpad where we took notes on today's meeting: https://etherpad.opendev.org/p/Digital-Sovereignty-WG The next meeting date and time is to be determined by you all! Here is the poll to vote <https://beta.framadate.org/polls/fe703653fdd969cbdaf4/1e0eba4bc789b7067aa1/…> on a date/time between Feb 17th, 18th, and 19th. *I will set the deadline to vote for the end of the previous week - February 13. * Lastly, I want to remind folks of the homework we discussed on the call - using some of the words and phrases we brainstormed (and any others that get added) to craft a stance on why OpenInfra and our projects are able to support digital sovereignty. For more information on this discussion, please watch the recording of the recent meeting. Thanks! -Kendall

1 4

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2026.1/R-6)
by Goutham Pacha Ravi 15 Feb '26

15 Feb '26

Hello Stackers, We're 6 weeks away from the date of the coordinated release of OpenStack 2026.1 "Gazpacho" [1]. We have a number of release deadlines scattered between this week and next, so it's an extremely busy time for project maintainers and our release management team. The nomination window for the combined TC and PTL elections is also closing this week (at 23:45 UTC on February 18, 2026) [2]. At last count, there were 27 project teams that still needed a PTL nominee. If you'd like to volunteer to be a PTL or if you think someone else should be, please ensure a nomination is submitted prior to the deadline. If you have questions regarding the process, please feel free to ask them on this mailing list or in the #openstack-election IRC channel on OFTC. The substantive governance activity in the past week was around the CI fixes concerning the regression in setuptools [3]. We've had to resurrect some "x-static" repositories in order for the OpenStack Dashboard project team to work around the changes from the upstream Python community. We're beginning to define the tested runtimes for the OpenStack 2026.2 "Hibiscus" release cycle [4]. Please take a look and give us your feedback. === Weekly Meeting === The last weekly meeting of the OpenStack Technical Committee was held over IRC on February 10, 2026 [5]. We focused on our past action items, technical debt, and the ongoing election cycle. We have officially closed the chapter on Monasca by abandoning 173 open changes across several repositories, and conversely, we’re seeing a promising revival of Cyborg with a new PTL nominee and a fresh team structure. In the hope of staffing project teams that have a large cross-project impact, we've proposed PTL nomination directories for the Requirements and Oslo teams not just to solicit candidates, but to spark a discussion on how we better support these critical dependencies. We discussed navigating a "borked" gate due to the recent setuptools' pkg_resources deprecation [3]. While we are currently merging "band-aid" pins to restore CI stability on stable branches, the situation would have been significantly worse without the proactive work done by Stephen Finucane (stephenfin) and Takashi Kajinami (tkajinam) over the last few months. Their foresight has saved project teams from a much larger headache during the feature freeze rush that's underway. Finally, we called out to project teams to review the User Survey streamlining plan [6]. Our goal is to refine this feedback loop prior to the PTG in April [7] so we can make timely improvements. The next meeting of the OpenStack Technical Committee is on Tuesday, February 17, 2026. This meeting is being held at 0800 UTC, a time that's better suited for our contributors in the Eastern Hemisphere. Please feel free to add to the agenda on the meeting's wiki page, and thank you in advance for your participation [8]. === Governance Proposals === ==== Merged ==== - Add a script to abandon changes on retired repositories | https://review.opendev.org/c/openstack/governance/+/975594 - Onboard additional xstatic packages | https://review.opendev.org/c/openstack/governance/+/976513 ==== Open For Review ==== - Define testing runtime for 2026.2 release | https://review.opendev.org/c/openstack/governance/+/976691 - Revert "Revive os_monasca" | https://review.opendev.org/c/openstack/governance/+/974775 === Upcoming Events === - 2026-02-26: 2026.1 "Gazpacho" Feature Freeze / Milestone 3 - 2026-03-10: OpenInfra Board Meeting: https://board.openinfra.org/ - 2026-03-23: KubeCon+Cloud Native Con EU begins: https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/ - 2026-04-20: OpenInfra PTG begins: https://openinfra.org/ptg/ === How to Contact the TC === You can reach the TC in several ways: 1. Email: send an email with the tag [tc] on this mailing list. 2. Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC. 3. Join us at our weekly meeting: The Technical Committee meets every Tuesday at 1700 UTC, except the third Tuesday of the month, when we meet at 0800 UTC [8]. Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2026.1 "Gazpacho" Release Schedule: https://releases.openstack.org/gazpacho/schedule.html [2] OpenStack "2026.2" Elections: https://governance.openstack.org/election/ [3] setuptools regression: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [4] Tested runtimes for 2026.2: https://review.opendev.org/c/openstack/governance/+/976691 [5] TC Meeting IRC Log, February 10 2026: https://meetings.opendev.org/meetings/tc/2026/tc.2026-02-10-17.00.html [6] Streamlining the OpenStack User Survey: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [7] OpenInfra PTG: https://openinfra.org/ptg/ [8] TC Meeting Agenda, February 17 2026: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[all][elections][ptl][tc] Combined PTL/TC 2026.2 cycle Election Nominations Last Days
by Ian Y. Choi 14 Feb '26

14 Feb '26

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Feb 18, 2026 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at[1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. All members of the community are encouraged to confirm their email address and opt in to the CIVS election as described at: https://governance.openstack.org/election/#electorate Election statistics[2]: Nominations started @ 2026-02-04 23:45:00 UTC Nominations end @ 2026-02-18 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 5 days, 0:17:37 Nominations progress : 64.20% --------------------------------------------------- Projects[1] : 40 Projects with candidates : 13 ( 32.50%) Projects with election : 1 ( 2.50%) --------------------------------------------------- Need election : 1 (Horizon) Need appointment : 27 (Adjutant Barbican Cinder Cloudkitty Heat Keystone Masakari Mistral Neutron Octavia OpenStackAnsible OpenStackSDK OpenStack_Charms Oslo Puppet_OpenStack Quality_Assurance Rally Requirements Skyline Storlets Sunbeam Swift Tacker Trove Venus Vitrage Zun) --------------------------------------------------- TC Candidates : 2 (5 Required) =================================================== Stats gathered @ 2026-02-13 23:27:23 UTC This means that with approximately 2 days left, 27 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.opendev.org/q/project:openstack/election+is:open+file:candid… have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0